Re: Re: Really odd PHP problem

From:	Sascha Schumann	Date:	Wed, 08 Sep 2004 11:50:11 +0000
Subject:	Re: Re: Really odd PHP problem
References:	1 2 3 4 5 6 7 8 9 10 11	Groups:	php.internals
Request:	Send a blank email to internals+get-12648@lists.php.net to get a copy of this message

On Wed, 8 Sep 2004, Joe Orton wrote:

On Wed, Sep 08, 2004 at 01:05:37PM +0200, Derick Rethans wrote:
On Wed, 8 Sep 2004, Joe Orton wrote:
Didn't Joe mean that it's wrong on Linux/x86_64 or am I misinterpreting his email?
Yup I did mean that. Linux/x86_64 is an example of a platform where you cannot put non-PIC code into a shared object. libtool does honour -prefer-non-pic on this platform, and hence will create broken shared objects. Therefore I would presume that -prefer-non-pic is not safe to use by default in the hope that libtool will prevent you shooting yourself in the foot.
Why can't we simply see this as a libtool bug?
If -prefer-non-pic flag is documented in libtool to mean "only build non-PIC code on platforms where it is safe to link such code into shared objects", then that would be reasonable, but I don't think that is the case.

    Yep.

Regardless, doing this is safely just requires a case $host in i?86-*) whitelist, I guess.

    So far, editing libtool and removing -fPIC has always
    worked for me. :-)

    - Sascha