On 13-08-25 07:07 PM, Mark Polesky wrote:
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
When I compile, I generally use -j3 CPU_COUNT=3 on a dual-core machine,
with no font issues that I've seen.
Cheers,
Colin
--
I've learned that you shouldn't go through life with a catcher's mitt on both
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
