Running under Snow Leopard

[Peter Leschev-2]

Hi,

          I noticed a few mails saying that lilypond does not run using Snow
Leopard. On a fresh machine, I installed 2.13.6 and experienced the endless loop
while constructing the font list. I removed this version & installed 2.12.2 and
it ran successfully

Cheers,
Peter



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

[Patrick McCarty-3]

On 2009-10-28, Peter Leschev wrote:
>
> I noticed a few mails saying that lilypond does not run
> using Snow Leopard. On a fresh machine, I installed 2.13.6
> and experienced the endless loop while constructing the
> font list. I removed this version & installed 2.12.2 and
> it ran successfully

Thanks for your report.

At this point, we can only speculate about the reasons why 2.12.2
works but 2.13.6 does not, because 2.12.2 was built with GUB2 (no
longer exists) and 2.13.6 was built with GUB3.

Many changes were made between GUB2 and GUB3, including dependency
updates, etc. etc.  It would be extremely difficult to track down the
problem this way.  And the problem might not be with GUB after all.


Here are some items I've noted while trying to debug this:

1) The "endless" loop occurs during the font caching stage while
processing the LastResort.ttf font.

2) On OSX 10.5 (Leopard), the LastResort.ttf font does not exist.
There is a LastResort.dfont instead.

3) I don't know if it makes a difference, but here are the size
differences between LastResort.{dfont,ttf}

  LastResort.dfont =  2.5MB
  LastResort.ttf   = 14.0MB

4) There was a recent change in Fontforge that involved the LastResort
font.  This might have been a related problem.  See
 
  http://fontforge.sourceforge.net/changelog.html

5) I took many "samples" with the Activity Monitor to see if that
would provide any leads, with no luck.  Everything branched from
FcConfigBuildFonts(), as I initially suspected (see font-config.cc).

***

There are three applications that would be helpful in debugging
further, but I don't have the privileges to install/use these
programs:

1) dtrace
2) Instruments (part of Xcode)
3) gdb

If you or anyone else running Snow Leopard can report any more
observations with help from these tools, or other debugging tools,
that would be wonderful.


Thanks,
Patrick


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

[Graham Percival-3]

On Wed, Oct 28, 2009 at 03:28:45PM -0700, Patrick McCarty wrote:
> At this point, we can only speculate about the reasons why 2.12.2
> works but 2.13.6 does not, because 2.12.2 was built with GUB2 (no
> longer exists) and 2.13.6 was built with GUB3.

Didn't we find that the 2.12.3 pre-release failed as well?  If I'm
remembering correctly, then the problem would either be in GUB3 or
in whatever patches were backported.

A slight possibilty would be the updated lilypad app, or the way
that app was bundled?

Cheers,
- Graham


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

[Patrick McCarty-3]

On 2009-10-28, Graham Percival wrote:
> On Wed, Oct 28, 2009 at 03:28:45PM -0700, Patrick McCarty wrote:
> > At this point, we can only speculate about the reasons why 2.12.2
> > works but 2.13.6 does not, because 2.12.2 was built with GUB2 (no
> > longer exists) and 2.13.6 was built with GUB3.
>
> Didn't we find that the 2.12.3 pre-release failed as well?  If I'm
> remembering correctly, then the problem would either be in GUB3 or
> in whatever patches were backported.

Oh, yeah.  :-)  I think you're right.

Would it be possible to build an installer from the release/2.12.2
commit in stable/2.12?

If that installer also hangs, then it's likely a GUB problem.

> A slight possibilty would be the updated lilypad app, or the way
> that app was bundled?

The hang occurs even when LilyPad is not used, so I doubt this is the
problem.

-Patrick


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

[Patrick McCarty-3]

On 2009-10-28, Patrick McCarty wrote:

> On 2009-10-28, Graham Percival wrote:
> > On Wed, Oct 28, 2009 at 03:28:45PM -0700, Patrick McCarty wrote:
> > > At this point, we can only speculate about the reasons why 2.12.2
> > > works but 2.13.6 does not, because 2.12.2 was built with GUB2 (no
> > > longer exists) and 2.13.6 was built with GUB3.
> >
> > Didn't we find that the 2.12.3 pre-release failed as well?  If I'm
> > remembering correctly, then the problem would either be in GUB3 or
> > in whatever patches were backported.
>
> Oh, yeah.  :-)  I think you're right.
>
> Would it be possible to build an installer from the release/2.12.2
> commit in stable/2.12?
>
> If that installer also hangs, then it's likely a GUB problem.

Maybe we could try bumping Freetype and Fontconfig to the latest
releases?  IIRC, GUB is using an old version of Freetype.

-Patrick


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

[Graham Percival-3]

On Thu, Oct 29, 2009 at 10:12:47AM +1100, Peter Leschev wrote:
>                    I'm happy to try 2.12.3 pre-release - is it publicly
>    available? Can't find it here:
>    http://download.linuxaudio.org/lilypond/binaries/darwin-x86/

Since it's a pre-release, no, it's not available there.  When I
make a new one, it would go in
  http://lilypond.org/~graham/

And no, this is not an official site for release tests, so there's
absolutely no point putting the link anywhere on the website.

Cheers,
- Graham


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

[Graham Percival-3]

On Wed, Oct 28, 2009 at 03:46:00PM -0700, Patrick McCarty wrote:
> On 2009-10-28, Patrick McCarty wrote:
> > On 2009-10-28, Graham Percival wrote:
> > > Didn't we find that the 2.12.3 pre-release failed as well?  If I'm
> > > remembering correctly, then the problem would either be in GUB3 or
> > > in whatever patches were backported.
> >
> > Would it be possible to build an installer from the release/2.12.2
> > commit in stable/2.12?

Hmm.  I'm not optimistic, especially since Jan seems to be away
this week.

> > If that installer also hangs, then it's likely a GUB problem.
>
> Maybe we could try bumping Freetype and Fontconfig to the latest
> releases?  IIRC, GUB is using an old version of Freetype.

This is likely to cause other problems, but sure, I'm willing to
try this.  I'll cut a 2.12.3 test with the latest
freetype+fontconfig tomorrow.

Cheers,
- Graham


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

[Graham Percival-3]

On Wed, Oct 28, 2009 at 03:46:00PM -0700, Patrick McCarty wrote:
> On 2009-10-28, Patrick McCarty wrote:
> > Would it be possible to build an installer from the release/2.12.2
> > commit in stable/2.12?
>
> 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.

I'll come back to university and give it a shot on Sat night; I
don't have any halloween plans.

Cheers,
- Graham


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

[Patrick McCarty-3]

On 2009-10-30, Graham Percival wrote:

> On Wed, Oct 28, 2009 at 03:46:00PM -0700, Patrick McCarty wrote:
> > On 2009-10-28, Patrick McCarty wrote:
> > > Would it be possible to build an installer from the release/2.12.2
> > > commit in stable/2.12?
> >
> > 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.
>
> I'll come back to university and give it a shot on Sat night; I
> don't have any halloween plans.

No rush.  I won't be able to test any darwin installers until Monday
anyway.

Thanks,
Patrick


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

[Graham Percival-3]

On Fri, Oct 30, 2009 at 4:32 PM, Graham Percival
<graham@...> 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?

Cheers,
- Graham


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

[Patrick McCarty-3]

On Sat, Oct 31, 2009 at 11:42 AM, Graham Percival
<graham@...> wrote:

> On Fri, Oct 30, 2009 at 4:32 PM, Graham Percival
> <graham@...> 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@...
http://lists.gnu.org/mailman/listinfo/bug-lilypond

[Graham Percival-3]

On Sat, Oct 31, 2009 at 03:16:56PM -0700, Patrick McCarty wrote:
> 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.

Hah!  Not only did I spend an hour trying to build fontforge
yesterday, but today I spent at least 15 minutes trying to figure
out why modifying gub/specs/fontconfig.py didn't change the
configure options when building freetype.py.

At long last, though I present 2.13.7 for darwin-x86, made with
freetype 2.3.11 and fontconfig 2.7.3.

http://lilypond.org/~graham/


I don't know how to pick out just darwin-x86 for a 2.12 build, and
making all the 2.12 stuff will take a while.  If it's finished
before I go home tonight, I'll upload it, but it's more likely
that it won't go up until tomorrow (Monday).

Cheers,
- Graham


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

[Patrick McCarty-3]

On Sun, Nov 1, 2009 at 9:07 AM, Graham Percival
<graham@...> wrote:
> On Sat, Oct 31, 2009 at 03:16:56PM -0700, Patrick McCarty wrote:
>> 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.
>
> At long last, though I present 2.13.7 for darwin-x86, made with
> freetype 2.3.11 and fontconfig 2.7.3.
>
> http://lilypond.org/~graham/

Great!  That fixed font caching problem on Snow Leopard (for me).
Tested from the command line and the GUI.  Thanks for doing that.

LilyPond itself seems to work fine; the only odd thing I'm
experiencing are Pango-WARNING messages:

  (process:1380): Pango-WARNING **: Error loading GSUB table 0x6EAD
  (process:1380): Pango-WARNING **: Error loading GPOS table 0x6EAD

but the output seems to be unaffected.  Things like this have been
reported before, like

  http://code.google.com/p/lilypond/issues/detail?id=752
  https://bugzilla.gnome.org/show_bug.cgi?id=577952

Apparently, that Pango bug was fixed in 1.24.1, so maybe it's a
regression?  I'll test on Leopard in a second.


Thanks,
Patrick


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

[Graham Percival-3]

On Sun, Nov 01, 2009 at 11:03:55AM -0800, Patrick McCarty wrote:
> On Sun, Nov 1, 2009 at 9:07 AM, Graham Percival
> <graham@...> wrote:
> > At long last, though I present 2.13.7 for darwin-x86, made with
> > freetype 2.3.11 and fontconfig 2.7.3.
>
> Great!  That fixed font caching problem on Snow Leopard (for me).
> Tested from the command line and the GUI.  Thanks for doing that.

That's good, because the 2.12 build isn't going so smoothly... for
some reason it was refusing to substitute
  doc/v2.12/
in a file that definitely contained it.  I took out the
"must-succeed" check, but this seems like a cheating solution.

> Apparently, that Pango bug was fixed in 1.24.1, so maybe it's a
> regression?  I'll test on Leopard in a second.

We currently use pango 1.24.4, which was released on... actually,
30 June.  The latest pango is 1.26, releasd on 21-sep-2009.
*shrug*

After checking that the freetype/fontconfig, err, fontforge...
no wait, I was right the first time.


Whatever.  If the current stuff works for other OSes as well, I
could try bumping pango.  I'm going home now, though.

Cheers,
- Graham


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

[Patrick McCarty-3]

On Sun, Nov 1, 2009 at 11:21 AM, Graham Percival
<graham@...> wrote:
> On Sun, Nov 01, 2009 at 11:03:55AM -0800, Patrick McCarty wrote:
>
>> Apparently, that Pango bug was fixed in 1.24.1, so maybe it's a
>> regression?  I'll test on Leopard in a second.
>
> We currently use pango 1.24.4, which was released on... actually,
> 30 June.  The latest pango is 1.26, releasd on 21-sep-2009.
> *shrug*

Bumping Pango could fix the problem.  Maybe there were some fixes for
compatibility with recent Freetype releases, or something like that.
I'm seeing the same error messages on Leopard now, but again with no
detectable changes in the PDF output.

Thanks,
Patrick


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

[Jan Nieuwenhuizen]

Op zaterdag 31-10-2009 om 18:42 uur [tijdzone +0000], schreef Graham
Percival:
> On Fri, Oct 30, 2009 at 4:32 PM, Graham Percival
> <graham@...> 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

>    libtool: compile: unable to infer tagged configuration
>    libtool: compile: specify a tag with `--tag'

I presume this has been resolved while I was "studying" to become
a snowboard intstructor.  However, see freetype.py for a libtool
tag=.. fixup.

Apropos updating, see bin/gupdate :-)

Jan.

--
Jan Nieuwenhuizen <janneke@...> | GNU LilyPond - The music typesetter
Avatar®: http://AvatarAcademy.nl    | http://lilypond.org



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