On 13-08-27 09:16 AM, Phil Holmes wrote:
"Mark Polesky" <markpole...@yahoo.com> wrote in message
news:1377597745.14398.yahoomail...@web181404.mail.ne1.yahoo.com...
In case anyone is still interested in this, today I
completely cleaned out my source dir and did a `make' and
`make doc' (no `-j5' or `CPU_COUNT=5'), from scratch with
latest master:
rm -rf ~/lilypond-git/* && git reset --hard origin/master
./autogen.sh --noconfigure
mkdir build/
cd build/
../configure
make
make doc
...and still I get these weird sans-serif fonts in the doc
png images. So it's clearly *not* related to the `-j' and
`CPU_COUNT' options. I don't really need to be building LP
for the type of work that I usually do, but it is a little
disappointing that I couldn't create a proper release if I
wanted to. I also find it strange that others with a very
similar system (Ubuntu 64bit) do not have this problem.
I don't think I compiled LP last since 2.13.12 or so, but if
I ever track down a specific regression point, I'll be sure
to post it here.
- Mark
==========================================
What happens if you just use your compiled version of LilyPond to
compile some music with lyrics?
Another possibility is that your font cache is munged, Mark. I've seen
discussions where a missing font was replaced with a generic sans face.
Regrettably, I can't point to the location of a font cache on my Linux
Mint machine; it should be in ~/.lilypond-fonts.cache-2 but that seems
to have changed. It may well be worth tracking down the cache on your
machine and deleting it, which will force LilyPond to rebuild it next
time it runs.
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
