So yes, I was able to recreate the problem.
1) start from scratch - delete ~/.fontconfig
2) run lilypond 2.10.11-1 - File compiles normally, expected output
3) run lilypond 2.10.19-1 Receive error output:

"No fonts found; this probably means that the fontconfig
library is not correctly configured. You may need to
edit the fonts.conf configuration file. More information
about fontconfig can be found in the fontconfig(3) manual
page and on http://fontconfig.org";

4) delete ~/.fontconfig
5) run lilypond 2.10.19-1 - file compiles normally, expected output

or

4) upgrade to 2.10.20-1 Problem solved


Am 26.02.2007 um 22:46 schrieb Graham Percival:

I've been updating my versions on OSX for over a year, and this is the first time I've had to do it. If this problem only occurs on the devel side, I have no sympathy for other OSX users. If it occurs in stable, then we obviously need to fix it.

(no, it's not part of the regular update process)


...
whoops, I just noticed that this _was_ a problem for stable versions. Argh, I've lost track. Did you have any problems with only stable versions, or did you only have problems with 2.10 after playing around with 2.11?

Cheers,
- Graham



_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to