hi,
On Sat, Jul 21, 2001 at 10:49:23PM +0200, Juergen Hasch wrote:
>
> libacl.a is a static library that is used only at compile time. This is
> because libacl.a contains only the stubs for libacl.so.
No, this is not correct. libacl.a provides everything that libacl.so
does, in terms of ACL code. A program can link against either the
shared or the static version of the library - it is not necessary to
have the other present at all at build time. Previously we _only_
provided a static library for libacl (and libattr, and libdm, and...)
but we now provide both. We now use the GNU libtool package to help
with building these libraries, which we also did not do before.
> No-one has *.a files in /lib, they are all in /usr/lib. Take a look in your
> /lib directory. You find the stubs for e.g. libc as /usr/lib/libc.a, but
> the actual libc.so in /lib.
That may be how libc works (I don't know, the stubs thing sounds like a
very strange thing to do), but that isn't how most static libraries work
and is not how libacl.a works.
> So you need libacl.so in /lib and libacl.a in /usr/lib.
>
This assertion is not correct - you may be misunderstanding
some of the mechanics of libraries - the libtool documentation,
ld(1), and ar(1) man pages might help.
Having said all that, I do agree that the static libraries should
go into /usr/lib - its just a matter of coercing libtool to put them
there or changing our own install process - I'll have a look into it
sometime this week.
Thanks for the input.
cheers.
--
Nathan
|