is allow_nonpic_in_shlib still useful? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject is allow_nonpic_in_shlib still useful?
Date
Msg-id 1355552618.7997.7.camel@vanquo.pezone.net
Whole thread Raw
Responses Re: is allow_nonpic_in_shlib still useful?  (Noah Misch <noah@leadboat.com>)
Re: is allow_nonpic_in_shlib still useful?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
In the plperl and plpython makefiles we look for a shared library of
libperl or libpython, and if it's not found, we check for
allow_nonpic_in_shlib, and if that's yes, then we proceed anyway.
Apparently, and IIRC, this was set up in a time when those shared
libraries were not available through standard builds, but I think that
hasn't been the case for quite a while.

The only platforms where we set allow_nonpick_in_shlib is linux and
freebsd/i386 (presumably an obsolescent combination).  Are there any
Linux builds that don't supply the required shared libraries?

I suspend this hack isn't useful anymore and ought to be removed.





pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Doc patch to note which system catalogs have oids
Next
From: "Erik Rijkers"
Date:
Subject: small pg_basebackup display bug