David Kastrup wrote:
As I mentioned earlier, my font problem only happens on
2.17.25. The output on 2.17.24 is fine.
There is no real candidate for such a difference in the
commits. So did you choose a significantly different
directory name for building 2.17.25?
No. I haven't built lilypond in well over a year (maybe
two); everything was built from a clean environment. I just
did a fresh build from a brand-new build dir, and the
problem persists. Also, the new 2.17.25 release from the
downloads directory on the website works fine for me; it's
only when I build the docs myself that I get this problem.
So I'm starting to supsect that this is related to my use of
the -j and/or CPU_COUNT options:
make -j5
make -j5 CPU_COUNT=5 doc