lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUB experiments on linux-64


From: Josh Parmenter
Subject: Re: GUB experiments on linux-64
Date: Tue, 30 Sep 2008 09:32:28 -0700

Hi Han-Wen,

otool looks okay:

Ringo:bin joshp$ otool -L lilypond
lilypond:
@executable_path/../lib//libintl.8.dylib (compatibility version 9.0.0, current version 9.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.2) @executable_path/../lib//libguile.17.dylib (compatibility version 19.0.0, current version 19.2.0) @executable_path/../lib//libgmp.3.dylib (compatibility version 8.0.0, current version 8.1.0) @executable_path/../lib//libpangoft2-1.0.0.dylib (compatibility version 2001.0.0, current version 2001.0.0) @executable_path/../lib//libpango-1.0.0.dylib (compatibility version 2001.0.0, current version 2001.0.0) @executable_path/../lib//libfreetype.6.dylib (compatibility version 10.0.0, current version 10.8.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) @executable_path/../lib//libfontconfig.1.dylib (compatibility version 5.0.0, current version 5.0.0) @executable_path/../lib//libgobject-2.0.0.dylib (compatibility version 1601.0.0, current version 1601.1.0) @executable_path/../lib//libgmodule-2.0.0.dylib (compatibility version 1601.0.0, current version 1601.1.0) @executable_path/../lib//libglib-2.0.0.dylib (compatibility version 1601.0.0, current version 1601.1.0) /usr/lib/libiconv.2.dylib (compatibility version 5.0.0, current version 5.0.0) @executable_path/../lib//libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)

I do have opt/local/ in my load path, and I also have /opt/local/lib in my DYLD_LIBRARY_PATH env var. But I don't see why lilypond would be following those before its own linked libs...

Yes... after the first run, things are faster.

Best,

Josh

On Sep 30, 2008, at 7:12 AM, Han-Wen Nienhuys wrote:

On Tue, Sep 30, 2008 at 12:46 AM, Josh Parmenter <address@hidden > wrote:
Here is what I have figured out. I renamed my opt folder (that contains my own guile, etc.), and the crash disappears. But, then the command line app simply hangs on even the simplest ly file for about three minutes, then
eventually compiles:

{
c' e' g' e'
}

However, if I move opt back, the crash occurs again. The most stripped down
crash report is below.

It seems that the lilypond .app for some reason is linked to the /opt
directory.  Can you figure out why?  Do you have /opt in any
environment variable?  Can you inspect the linkage of the binary
(IIRC, you can inspect the dylibs with otool).

The delay is most likely a font caching problem; doesn't it speed up
after the 1st run?

This was probably masked by the fact that previous .apps were using
the PPC architecture.


--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen

******************************************
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/

“Every composer – at all times and in all cases – gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]