Hi Ralf, Hate to admit it, but this is really embarrassing. I started to create the info you requested, e.g., the libtool --features (host: i586-pc-linux-gnu, enable shared libraries, enable static libraries), then went on to investigate my log files once more to see if I could elaborate a bit more on my example. I then realized that I had gone down a completely wrong path: I guess the libtool documentation I referenced confused me a bit + I failed to see a few really clear lines in the logs that should have made me realize that libtool was in fact working as it should. Embarrassing.
The actual problem was a (non-libtool) archive of non-PIC code being linked into a couple of the shared libraries. The package I'm building has dependencies to already installed libraries and one of these libraries was by mistake only installed as an archive of non-PIC code (due to me not reading the fine print in the makefile for that library good enough). I guess this just shows that it makes compilation of packages somewhat more difficult if each package is trying to rely on its own makefile setup instead of using the GNU Autotools, which offer an almost uniform interface to its users across packages. Sorry for wasting your time. (However, I'm still curious about the wording of the libtool documentation that I referenced). Best regards, Bjarne Vestergaard On Monday 10 July 2006 22:45, Ralf Wildenhues wrote: > Hello Bjarne, > > .... > > Shouldn't happen. Please print the output of these commands... > > > I'm using libtool 1.5.22 with GCC on Linux (i686). The way I created the > > convenience library is as follows: > > > > libtool --mode=compile gcc -c libB.c -o libB.lo > > libtool --mode=link gcc libB.lo -o libB.la > > ... as well as the output of > libtool --features > libtool --config > > I assume the libtool you're using has been configured with > --disable-shared or so. > > .... > > Cheers, > Ralf, (don't wait for my next answer) _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
