Re: libwrap.a and -fPIC
On Tue, 26 Oct 1999, Adam C Powell IV wrote:
> Really? Last time I tried to check a static lib in autoconf it
> couldn't find it, I assumed that was because it was static and not
> shared. But I must have been doing something else wrong, or maybe
> autoconf has changed...
>
> Could this be considered a bug in autoconf/libtool? That is, wouldn't it be
> better if they just detected the shared/static lib, and automatically did the
> right thing (as I had assumed)?
No, because the "right thing" depends on the the specific situation.
> It seems like this is a generic problem, and ORBit isn't the only
> project which could benefit from this being done right.
>
> Suggested behavior: if the static lib is there and not the shared version,
> autoconf could pass the full path to the .a file as the "flag" instead of -lwrap,
> and then libtool -mode=link would see this, unpack the .a, and repack the objects
> into the new lib.
You're expecting libtool to be bright. :) libtool is really aweful to use
for everything except the basic 80% of cases. Its feature set is basically
the lowest common denominator of the available features on all supported
platforms.
-- Elliot http://developer.gnome.org/
The first thing a programmer needs to admit is that any program is by far
more complex than his own mind. Thats why he partitions it into neat
pieces and avoids complexity.
Reply to: