On Mon, Jul 30, 2001 at 03:03:23PM +0200, Florian Weimer wrote: > | The shared version must be compiled with -fPIC, and the static version must > | not be. In other words, each *.c file will need to be compiled twice. > > IMHO, it makes sense to drop this C reference as well, if we are in > the process of changing the section.
How much of a C reference is it? Code in shared libraries must be position independent. How it is achieved is less important, but I expect that it's going to involve a flag similar to -fPIC. And I don't want to replace it with a general statement about position independence, because that means more people will get it wrong. > In addition, there are some architectures where all code is position > independent, so -fPIC is a noop, and others, where -fPIC is less > efficient then -fpic. IIRC, policy specifies -fPIC specifically because -fpic does not work right on all architectures. I think that trying to prescribe different flags for different architectures will cause insanity. Remember, there's only one source package. -- Richard Braakman Will write free software for money. See http://www.xs4all.nl/~dark/resume.html
