Re: cvs tip broken build for plpython - Mailing list pgsql-hackers

From Tom Lane
Subject Re: cvs tip broken build for plpython
Date
Msg-id 21799.1097524224@sss.pgh.pa.us
Whole thread Raw
In response to Re: cvs tip broken build for plpython  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: cvs tip broken build for plpython
List pgsql-hackers
"Andrew Dunstan" <andrew@dunslane.net> writes:
>> On my FC3 installation, there is a /usr/lib/libpython2.3.so.1.0
>> ... do you have anything comparable?

> No, except the non-standard one on the openoffice libs. Building as shared
> lib only became a part of standard python in release 2.3 - see
> http://www.python.org/doc/2.3.4/whatsnew/node20.html

I've committed some changes to try to use the shared library where
available, while continuing to work if it isn't:

* If distutils reports values for LIBDIR and LDLIBRARY, and the latter
looks like a shared library name, then use -L$LIBDIR -l$LDLIBRARY (after
suitable hacking on the library name).

* Otherwise use -L$CONFIGDIR -lpython$VERSION.

The latter case duplicates what we have done in past versions, so it
should theoretically work as well (or poorly) as ever.  The test
conditions may still need fine-tuning though.  I do not have a pre-2.3
Python to try it with --- would you test please?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Unit testing
Next
From: Tom Lane
Date:
Subject: Re: Status ofTrigger Firing Order and 'FOR EACH STATEMENT'?