I think that policy needs two small corrections to reflect current practices wrt shared libraries and PIC code:
- what is PIC library needs to be correctly defined: compiling with -fPIC is not enough to have PIC code, the object MUST NOT have a TEXTREL section either [any other symbols need to be checked? What about non-i386 architectures?] - libraries can contain short sections of non-PIC code on architectures which allow this [i386 is OK, any other?] if this allows a significant speed increase. Everybody agrees? -- ciao, Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
