On 4/28/15 11:48 PM, Tom Lane wrote:
>> My preference would be to rip all that out and let the compiler or
>> linker decide when it doesn't want to link something.
>
> Works for me, assuming that we get an understandable failure message and
> not, say, a plperl.so that mysteriously doesn't work.
On Wed, Apr 29, 2015 at 12:48 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> On 4/28/15 12:05 AM, Tom Lane wrote:
>>> Yeah. Even more specifically, olinguito does have --with-python in its
>>> configure flags, but then the plpython Makefile skips the build because
>>> libpython isn't availabl
Peter Eisentraut writes:
> On 4/28/15 12:05 AM, Tom Lane wrote:
>> Yeah. Even more specifically, olinguito does have --with-python in its
>> configure flags, but then the plpython Makefile skips the build because
>> libpython isn't available as a shared library. But the contrib test is
>> (I ass
On 04/28/2015 04:31 PM, Peter Eisentraut wrote:
On 4/28/15 12:05 AM, Tom Lane wrote:
Yeah. Even more specifically, olinguito does have --with-python in its
configure flags, but then the plpython Makefile skips the build because
libpython isn't available as a shared library. But the contrib te
On 4/28/15 12:05 AM, Tom Lane wrote:
> Yeah. Even more specifically, olinguito does have --with-python in its
> configure flags, but then the plpython Makefile skips the build because
> libpython isn't available as a shared library. But the contrib test is
> (I assume, haven't looked) conditional
