On 4 Feb 2010, at 00:47, James Bailey wrote:
This may have to do with the order of things in your $PATH.
Possibly, unless 'lilypond' sets its own. But why is 'lilypond'
calling it? Library paths are hardcoded. And calling stuff that comes
with the OS should be called using full paths if it is an Application,
I think.
One possibility is that it calls "guile", but then its own libraries.
I noticed that breaking when installing the new guile. One shell tried
to call an old version, even though $(which guile) gave the path to
the new one.
LilyPond.app has its own
/Applications/LilyPond.app/Contents/Resources/bin/guile
It must be compiled so that the prefix is ../ or ./ or something.
One possibility is that not all LilyPond.app stuff has that. - It is
the same Guile 1.8.7 version, though.
Hans
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
