texlive-bin: clang hangs and leaks memory trying to build makejvf

[drkp (Dan Ports)]

As reported ​on the mailing list:

When building texlive-bin, attempts to compile texk/makejvf/main.c cause clang to hang and exhaust system memory. It looks like there are some illegal character encodings in that file.

I've observed this with the following clang version on 10.8.2:

Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.2.0
Thread model: posix

It's apparently version-specific, as I hadn't previously noticed this, and the buildbot didn't run into it, but I haven't narrowed it down any more yet.

[drkp (Dan Ports)]

Disabled building makejvf for now as a workaround: r104809.

[cooljeanius (Eric Gallager)]

I ran into this problem myself awhile ago and forked the texlive-bin portfile to add a +nomakejvf variant: ​https://github.com/cooljeanius/LocalPorts/blob/master/tex/texlive-bin/Portfile#L351

For the MacPorts portfile though I'd recommend just disabling makejvf unconditionally because there's actually a separate port for makejvf: see #38585 for more.

See also #38018 for when I ran into a similar issue with doxygen.

[cooljeanius (Eric Gallager)]

Cc Me!

[mojca (Mojca Miklavec)]

A question for those of you for whom it fails: does compilation of the latest TeX Live sources from SVN (​svn://tug.org/texlive/trunk/Build/source) also fail to work on your setup? I'm asking because there are about 2 weeks left to fix any problems before TeX Live sources will be frozen for the TL 2013 release (there might be a bit more time, but not that much).

[drkp (Dan Ports)]

Replying to mojca@…:

A question for those of you for whom it fails: does compilation of the latest TeX Live sources from SVN (​svn://tug.org/texlive/trunk/Build/source) also fail to work on your setup? I'm asking because there are about 2 weeks left to fix any problems before TeX Live sources will be frozen for the TL 2013 release (there might be a bit more time, but not that much).

I was going to try that yesterday but I had to wait for svn to finish checking out texlive trunk. :-)

It looks like it's still an issue. The questionable character encodings are in the usage() text for makejvf.

It also looks like adding -Wno-invalid-source-encoding to clang's cflags is a sufficient workaround, so there's that...

[drkp (Dan Ports)]

Re-enabled makejvf, using -Wno-invalid-source-encoding when building with clang, in r105371

[drkp (Dan Ports)]

As for whether we should just rely on the separate makejvf port, the question is whether that port provides the same version as the one in texlive. (Also, whether it's maintained, which it seems to be.)