On Sat, Oct 31, 2009 at 11:42 AM, Graham Percival <gra...@percival-music.ca> wrote: > On Fri, Oct 30, 2009 at 4:32 PM, Graham Percival > <gra...@percival-music.ca> wrote: >> On Wed, Oct 28, 2009 at 03:46:00PM -0700, Patrick McCarty wrote: >>> Maybe we could try bumping Freetype and Fontconfig to the latest >>> releases? IIRC, GUB is using an old version of Freetype. >> >> This'll be more complicated than I originally thought, since they >> have patches and stuff that don't apply cleanly to the updated >> version. > > Correction: freetype is just fine. The patch for fontforge just > removes the libxml2 stuff, which I don't understand since it depends > on libxml2 anyway. Disregarding that, though, I run into the dreaded > libtool: compile: unable to infer tagged configuration > libtool: compile: specify a tag with `--tag' > > This goes away if I manually add --tag=CC, but I'm really suspicious > of that solution... if libtool can't figure out that something is a .c > file by itself, it sounds like something is seriously wrong. > > Jan, could you take a look at updating fontforge?
Umm, I suggested that Fontconfig be updated, not Fontforge. It seems that the Snow Leopard problem stems from what happens after FcConfigBuildFonts() is called, and this is part of Fontconfig. Though I suppose it wouldn't hurt to bump Fontforge either. I want to add `--enable-double' to Fontforge, but since I currently can't compile LilyPond through GUB, I wouldn't be able to test it. Thanks, Patrick _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
