TeXLive 2014

[Hiroki Sato]

Greg Lewis <glewis at eyesbeyond.com> wrote
  in <20140823174220.GA46087 at misty.eyesbeyond.com>:

gl> After the TeXLive 2014 update a number of the tex related ports won't
gl> build.  An example is print/tex-aleph.  It currently dies like this:
gl>
gl> Transcript written on lamed.log.
gl> fmtutil: /usr/ports/print/tex-aleph/work/stage/usr/local/share/texmf-var/web2c/aleph/lamed.fmt installed.
gl> /bin/rm -f /usr/ports/print/tex-aleph/work/stage/usr/local/share/texmf-dist/ls-R /usr/ports/print/tex-aleph/work/stage/usr/local/share/texmf-var/ls-R /usr/ports/print/tex-aleph/work/stage/usr/local/share/texmf-dist/web2c/texmf.cnf
gl> /bin/rmdir /usr/ports/print/tex-aleph/work/stage/usr/local/share/texmf-dist/web2c || true
gl> ====> Compressing man pages (compress-man)
gl> ====> Running Q/A tests (stage-qa)
gl> Error: 'share/texmf-var/web2c/aleph/aleph.log' is referring to /usr/ports/print/tex-aleph/work/stage
gl> Error: 'share/texmf-var/web2c/aleph/lamed.log' is referring to /usr/ports/print/tex-aleph/work/stage
gl> *** Error code 1
gl>
gl> There are a number of other ports in the same boat.  In this case, and
gl> others where the errors are regarding log files, the errors are spurious.
gl> We shouldn't even install these log files since they serve no purpose and
gl> are just artifacts of the build.
gl>
gl> For other ports (e.g. japanese/tex-ptex) the errors seem much more serious:
gl>
gl> Error: 'share/texmf-var/web2c/euptex/uplatex.fmt' is referring to /usr/ports/japanese/tex-ptex/work/stage
gl>
gl> In this case the .fmt files are a needed file for things to work.
gl>
gl> I haven't yet looked into how to possibly fix these.  Can others reproduce?

 This is reproducible and has also been filed as PR 192933.  I am
 wondering if I should fix this and how to do it if should.  I agree
 that it is better to fix them if possible, but it is harmless in this
 case and difficult to properly fix it.

 foo.fmt and foo.log which are generated for a TeX format "foo".  They
 contain ${STAGEDIR} because they are processed within the directory,
 but they are just recorded, not used as pathname.  Although we can
 replace the pathnames by using sed(1) in foo.log since it is a plain
 text, it is difficult for foo.fmt.

 One way to fix it is to run fmtutil after necessary texmf files
 installed.  However, .fmt file generation in ${STAGEDIR} is
 friendlier with packaging and safer in terms of possible failures
 (i.e. errors can be detected before installing).

 For whether installing .log file or not, I intentionally installed
 them because the output is required for diagnostic purpose.  Building
 a .fmt can be screwed up in various ways without compile-time error
 even if taking countermeasures, and it is difficult to detect
 malformed one without .log.

-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20140824/00c7c90d/attachment.sig>