[Charles Wilson] Re: libtool bug

[Han-Wen Nienhuys <hanwen at xs4all dot nl>]

janneke@gnu.org writes:
> > /home/Hanwen/src/guile-1.7.1/libguile/.libs; however,
> > running GCC with
> > 
> >   -L/home/Hanwen/src/guile-1.7.1/libguile/.libs -lguile
> > 
> > does work, so libtool is incorrectly translating the commandline.
> > I take that I don't need to run GCC with  -Wl,verbose  ? 
> > 
> 
> /home/Hanwen/src/guile-1.7.1/libguile/.libs
> /home/Hanwen/src/guile-1.7.1/libguile-ltdl/.libs
> 
> Hmmm...it appears the real problem is the renaming of the source 
> directory, from libguile to libguile-ltdl.  I've seen libtool do that 
> sort of thing for single .c files (creating new versions of foo.c as 
> .libs/foo-ltdl.c, etc.  It does this when compiling different versions 
> of the same file with different AM_CFLAGS) but I have NEVER, EVER seen 
> it rename a directory.
> 
> This smells like a Makefile.am bug, or an automake bug, actually...

I think I have been confusing you. Guile used to come with its own
bindings to the ltdl library (indeed, it still ships a private copy of
ltdl, which doesn't compile on cygwin ATM). The GUILE stuff for ltdl
lives in the directory libguile-ltdl/ , while the core GUILE library
itself lives in libguile/

The proper command line for linking this srfi DLL includes 

*   -lltdl

(which links the system libltdl)

* libguile-ltdl.dll.a

(the GUILE wrapper around ltdl)

* libguile.dll.a

(the GUILE library itself)



-- 

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


--
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/