I really hope somebody (Jan? Han-Wen Nienhuys?) will try their guile build with unmodified libtool-1.5.10, and when the relink fails manually execute
> gcc -shared .libs/srfi-1.o -L/lib -L/usr/lib > -L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs -L/usr/local/lib > -lguile -lpthread -lgmp -lcrypt -o > .libs/cygguile-srfi-srfi-1-v-2-2.dll -Wl,--image-base=0x10000000 > -Wl,--out-implib,.libs/libguile-srfi-srfi-1-v-2.dll.a
from the appropriate directory, but adding "-v -Wl,-verbose" for verbose output from both gcc and ld. When THAT fails, figure out why it can't find libguile.dll.a in /home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs, because if it is there, it really ought to be able to find it given
-L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs -lguile
Okay?
-- Chuck
Charles Wilson wrote:
Jan Nieuwenhuizen wrote:
Do you have an insight wrt the start of this thread? That's stalling a Guile-1.7/libguile16 release and with it the LilyPond 2.3 series.
No, I don't. This:
gcc -shared .libs/srfi-1.o -L/lib -L/usr/lib -L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs -L/usr/local/lib -lguile -lpthread -lgmp -lcrypt -o .libs/cygguile-srfi-srfi-1-v-2-2.dll -Wl,--image-base=0x10000000 -Wl,--out-implib,.libs/libguile-srfi-srfi-1-v-2.dll.a
ought to succeed, IF /home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs contains any of the following:
libguile.dll.a guile.dll.a libguile.a cygguile.dll libguile.dll guile.dll
That's what -L/home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs -lguile MEANS, after all.
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/