libtool -fpic woes

[Marc Espie]

It's worse than I originally thought.

As I started earlier, gcc -shared needs to be passed the code generation
flag to work.

On multi-libbed systems, things get even worse. Namely, gcc -shared -fpic
might give you one path to the system libraries
(case in point : -L/usr/lib/gcc-lib/i386-unknown-openbsd2.8/fpic
-L/usr/lib/gcc-lib/i386-unknown-openbsd2.8)
which is utterly inappropriate for linking static libraries without -fpic.

Considering that libtool may wish to build static modules without -fpic,
it does need the same notion for static unshared libraries.

But there is just one compiler_lib_search_path variable, whereas this
*really* must be indexed on the code generation option used, for anything
on multi-libbed systems to have a chance to work...

Ouch.