On 2 Feb 2010, at 17:52, Bob Friesenhahn wrote:
Under OS-X (Leopard and later), the 'dtruss' program can be used to
see what is really going on.
While at it, I found another problem involving libltdl.7.dylib,
guile-1.8.7 and lilypond 2.13.7:
When upgrading guile using libtool-2.2.6b, lilypond broke, the one
which is in an Application distribution:
/Applications/LilyPond.app/Contents/Resources/bin/guile
It has its own
/Applications/LilyPond.app/Contents/Resources/lib/libltdl.7.dylib
However, dtruss shows that segmentation fault is caused when calling
/usr/local/lib/libltdl.7.dylib
When I move this to another name, then lilypond works, but dtruss now
shows that it calls
/usr/lib/libltdl.7.dylib
So it seems lilypond never calls its own libltdl.7.dylib.
The problem here, though, is the combination of incompatible versions
of libltdl.7.dylib in combination with a library search path. If they
really are incompatible, there seems to be no point in having a
searchpath.
I think that gcc on Mac OS X makes hardcoded full paths for libraries.
So libtool would then implement its own library search paths.
Also, it seems having no problem open .dylib files here.
Hans