Well, I usually go with stable versions unless someone says something is fixed in a development version, so most likely the first version I downloaded was 2.10.19-1, and then started other versions from there. That was the first version. Then I downloaded the development version, thinking that the problem may have been fixed. It wasn't, so I posted, and per Han-Wen, downloaded older versions until I came to one that would compile. 2.10.13-1, IIRC. Then, per Graham's instructions, I renamed and moved my .fontconfig file, and lilypond works fine now, both development and stable. I think I can recreate the circumstances under which the error occurs. I'll try it and let you know.
On Monday, February 26, 2007, at 10:46PM, "Graham Percival" <[EMAIL PROTECTED]> wrote: >James E. Bailey wrote: >> Thank you, this worked. So, do I have to delete the .fontconfig file >> everytime I use a new version? I mean, is this going to be a regular >> part of the update process? 'cause the average macintosh user doesn't >> know how to find hidden files. > >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
