Re: [Fwd: libwrap.a and -fPIC]
>The relevance to debian arm: one suggested workaround to the ORBit
>problem is to build libwrap.a with -fPIC. How feasible is this?
It would work, and it's feasible, but it's ugly and I don't think it should be
necessary.
>Looking at the Makefile in src/IIOP, I see LIBWRAP_PATH=/usr/lib/libwrap.a.
>This is because the toplevel configure.in looks only for libwrap.a. It seems
>more intelligent to just use the usual autoconf check for the libwrap.so and
>include this as a dependency, and then resort to ripping the objects out of
>libwrap.a only if it isn't there. Why the bizarre make_libwrap_files kludge?
Why can you not just use -lwrap and let the linker do the right thing? This
is the right way to handle libraries that depend on other libraries.
p.
Reply to: