Re: Use of -fPIC on Tru64

[Arnaud Charlet <charlet at ACT-Europe dot FR>]

> The message I replied to was something along "There are
> implementations where you do not need PIC to load a shared library, so
> there is no need to require PIC". You didn't say anything about Tru64
> (though you did in a previous message), and I was nitpicking. Kind of.

Well obviousely this is non very helpful and non constructive, since the
subject line of this thread couldn't be clearer. Also if I were to
nitpick, I would say that you didn't read the message you quoted very carefully
because I said "shared library", and not "dynamic library", but I won't.

I guess if noone answered that nobody is really interested in discussing it.

I still haven got a clear answer as to why this change has been made in GCC.

Was it a deliberate choice, or a general change ?

As a result of this change, we can no longer rely on LIBGCC2_FLAGS to build
other shared libraries in GCC (e.g for GNAT) in a simple way on Tru64, which
is inconvenient, but I guess unavoidable.

So let me phrase my question differently: is there a configure flag/setting
that can be reused in Makefiles to know whether a target absolutely
needs -fPIC to build a shared library ?

Arno