One can use 'dtruss lilypond empty', which the writes the stuff below.
So for some reason, lilypond does call stuff in /usr/local/lib/. And
it seems, as I thought, that it is libltdl that is the problem - I
used a different version.
The Guile manual, sec. 4.2.1, says that it uses LTDL_LIBRARY_PATH to
load extensible libraries. Perhaps it is used for all stuff - checking
the output of dtruss a bit further, reveals that it is only guile
calling stuff in /usr/local/lib/.
And I have not set that variable in my environment.
Hans
----
...
stat("/usr/local/lib/libltdl.7.dylib\0", 0xBFFF91F0, 0xBFFFACA8)
= 0 0
open("/usr/local/lib/libltdl.7.dylib\0", 0x0, 0x0) = 10 0
pread(0xA, "\376\355\372\316\0", 0x1000, 0x0) = 4096 0
mmap(0xD1C000, 0x7000, 0x5, 0x12, 0xA, 0xFEEDFACEDEAFBEAD) =
0xD1C000 0
mmap(0xD23000, 0x1000, 0x3, 0x12, 0xA, 0xFEEDFACEDEAFBEAD) =
0xD23000 0
mmap(0xD24000, 0x3F24, 0x1, 0x12, 0xA, 0xFEEDFACEDEAFBEAD) =
0xD24000 0
fcntl(0xA, 0x2C, 0xFFFFFFFFBFFF8808) = 0 0
close(0xA) = 0 0
__sysctl(0xBFFFB288, 0x3, 0xBFFFB278) = 0 0
sigprocmask(0x1, 0x0, 0x9FA074) = 0x0 0
sigaltstack(0x0, 0x9FA098, 0x9FA074) = 0 0
----
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
