Hi Marc, On Fri, Oct 2, 2009 at 2:31 PM, Marc Tyndel <jaz...@gmail.com> wrote: > 2009/10/2 Patrick McCarty <pnor...@gmail.com>: >> >> Thanks for your report! It's great to know that 2.12.2 (from the >> terminal) works on Snow Leopard. That really narrows down the >> problem. I suspect something may have broken in GUB... >> >> Specifically, does 2.13.3 halt at the "Building font database" step? > > I'm not entirely sure, how should I test that? I investigated in a > simple way: I went to the Activity Monitor, "Inspected" the Lilypond > process, looked at Open Files and Ports, and noted that it seemed > stuck on LastResort.ttf, which is a system font. Does that suggest the > problem is related to building the font database?
Yes, it does. > Keep in mind I am using 2.13.4 right now. After doing that first > compile with 2.12 I seem to be able to use the new version. Before > trying 2.12 I tested most of the 2.13.x releases and none worked. In your home directory, you'll find a directory named ".lilypond-fonts-cache", or something like that. This is the cache that Fontconfig creates when you run LilyPond for the first time when everything works correctly. Since an uninstall does not remove this directory, I think that explains why 2.13.4 is working for you now (since the database from 2.12.2 is still there). So, for some reason, I think something is wrong with Fontconfig on Snow Leopard (at least, as it's shipped with the default installer). > Let me know if there's anything I should test out. Sure. You can try running LilyPond with the --verbose flag and see where it stops. /path/to/lilypond --verbose file.ly It might be nice to see some sort of trace, too. On Linux, the "strace" tool works great, and maybe there is an application similar to it for Snow Leopard. Thanks for your help, -Patrick _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
