On Feb 7, 2002, "H . J . Lu" <[EMAIL PROTECTED]> wrote: > # gcc -fPIC -c foo.c > # ar rcs libfoo.a foo.o > # gcc -fPIC -c bar.c > # gcc -shared -o libar.so bar.o -lfoo -L.
> I don't want ANY dependency of libfoo.a in libbar.so. With the commands above, you don't get any dependency of libtool.a in libbar.so. I don't understand what you're complaining about. This doesn't even use libtool. > That is I can give libbar.so to someone. He/she can use it without > libfoo.a. With the current binutils in CVS, I got > /bin/sh ./libtool --mode=link gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes >-g -O2 -o libbfd.la -rpath /export/tools/lib -release 2.11.93 archive.lo >archures.lo bfd.lo cache.lo coffgen.lo corefile.lo format.lo init.lo libbfd.lo >opncls.lo reloc.lo section.lo syms.lo targets.lo hash.lo linker.lo srec.lo binary.lo >tekhex.lo ihex.lo stabs.lo stab-syms.lo merge.lo dwarf2.lo archive64.lo `cat ofiles` >-L../libiberty/pic -liberty > Did you see > dependency_libs=' -L/export/build/gnu/binutils-import/build-i686-linux/libiberty/pic >-liberty' Ah, ok, so it's the -liberty in libbfd.la that troubles you? If all you want is to be able to give libbfd.so to someone else, do so. You don't have to take libbfd.la along with it; just get rid of it. And make sure you don't give libbfd.a away either, because it's useless without the libiberty.a that you don't want to include in your package. > That is completely bogus for Linux. Nope, it's absolutely correct. Try to link with libbfd.la with -static, then drop -liberty from the command line you get and you'll see why. > Please fix it. You still haven't shown that there's anything to be fixed. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{cygnus.com, redhat.com} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
