Re: libtool searches '.' by default (was: unexpected emergence of --whole-archive)

2009-03-20 Thread Matěj Týč
> > It seems that the current build directory is implicitly passed as an > > -L. flag to the libtool-supervised linker > > No. Well, first off, until this message of yours, I didn't know that > /home/bubla/projects/devil_modular/lib/ was the current build directory. > > Hmm. This line in ltmain

libtool searches '.' by default (was: unexpected emergence of --whole-archive)

2009-03-18 Thread Ralf Wildenhues
* Matěj Týč wrote on Wed, Mar 18, 2009 at 01:41:37PM CET: > >> Maybe one question towards libtool maintainers is left: > >> Is that detection of lib/libjpeg.la a desired behavior? I just pass > >> -ljpeg as an LDFLAGG, not as a LIBADD library... > > > > Yes, it is.  It is also intentional that .la

Re: unexpected emergence of --whole-archive

2009-03-18 Thread Matěj Týč
>> Maybe one question towards libtool maintainers is left: >> Is that detection of lib/libjpeg.la a desired behavior? I just pass >> -ljpeg as an LDFLAGG, not as a LIBADD library... > > Yes, it is.  It is also intentional that .la files are installed > (of course for non-convenience archives only),

Re: unexpected emergence of --whole-archive

2009-03-16 Thread Ralf Wildenhues
Hello Matěj, * Matěj Týč wrote on Sun, Mar 15, 2009 at 08:20:19PM CET: > > Maybe one question towards libtool maintainers is left: > Is that detection of lib/libjpeg.la a desired behavior? I just pass > -ljpeg as an LDFLAGG, not as a LIBADD library... Yes, it is. It is also intentional that .la

Re: unexpected emergence of --whole-archive

2009-03-15 Thread Matěj Týč
> In the directory /home/bubla/projects/devil_modular/lib/ you have a > libjpeg.la file. This is not the jpeg module that you are creating, it > is a different library. libtool finds this when you pass -ljpeg (not > sure why, as there is no -L flag for that directory). This libjpeg.la is > a libtoo

Re: unexpected emergence of --whole-archive

2009-03-15 Thread Peter O'Gorman
Matěj Týč wrote: >>> /bin/sh ../libtool --tag=CC --mode=link gcc -DNOINLINE -Wextra -g -O0 >>> -module -ljpeg -o jpeg.la -rpath /usr/local/lib/IL jpeg_la-il_jpeg.lo >>> -lm -lz >>> results in: >>> libtool: link: gcc -shared .libs/jpeg_la-il_jpeg.o >>> -Wl,--whole-archive /home/bubla/projec

Re: unexpected emergence of --whole-archive

2009-03-15 Thread Matěj Týč
> > /bin/sh ../libtool --tag=CC --mode=link gcc -DNOINLINE -Wextra -g -O0 > > -module -lpng12 -o png.la -rpath /usr/local/lib/IL png_la-il_png.lo > > -lm -lz > > results in: > > libtool: link: gcc -shared .libs/png_la-il_png.o -lpng12 -lm -lz > > -Wl,-soname -Wl,png.so.0 -o .libs/png.so.0.

Re: unexpected emergence of --whole-archive

2009-03-15 Thread Peter O'Gorman
Matěj Týč wrote: > Hello, > I use autotools libtool to make a library. That library consists of the > main shared library file and a set of dynamically loadable modules. > Those modules depend on external shared libraries. > I have written configure.ac and Makefile.am that are quite complex and > s

unexpected emergence of --whole-archive

2009-03-15 Thread Matěj Týč
Hello, I use autotools libtool to make a library. That library consists of the main shared library file and a set of dynamically loadable modules. Those modules depend on external shared libraries. I have written configure.ac and Makefile.am that are quite complex and some things are generated duri