Subject: Re: CVS commit: pkgsrc
To: Nick Hudson <email@example.com>
From: Johnny C. Lam <firstname.lastname@example.org>
Date: 03/12/2001 11:57:52
Nick Hudson <email@example.com> writes:
> "Johnny C. Lam" wrote:
> > Create _pic.a libraries needed by forthcoming xerces-p package.
> > XXX This uses libtool internals!
> > Requested in private mail by Emmanuel Dreyfus <firstname.lastname@example.org>.
> Which reminds me...
> Why do you need it to be called _pic.a? Can't you just use the normal .a
> library created by libtool - all the objects are compiled with -fPIC
> -DPIC which is what you are after, right?. Unless I don't understand
> what you are trying to do - which is, of course, very likely.
My understanding of how libtool currently works is as follows. First,
libtool generates a directory .libs. Then during compilation, it
generates an object file compiled with PIC flags in ./.libs/foo.o and
an object file compiled without PIC flags in ./foo.o. Then during
linking, a shared library libfoo.so is created from ./.libs/*.o and a
static library libfoo.a is created from ./*.o. So libfoo.a is
composed of objects compiled _without_ the PIC flags.
-- Johnny C. Lam <email@example.com>
Department of Statistics, Carnegie Mellon University