From: | andrew(at)corvus(dot)biomed(dot)brown(dot)edu (Andrew Bosma) |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: State of PL/Python build |
Date: | 2001-05-13 03:25:42 |
Message-ID: | 20010512232542.A10336@corvus.biomed.brown.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 12, 2001 at 02:46:45PM -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > We already know about the libpython (not-)shared library issue. As it
> > turns out, not only is libpython generally not a shared library, there
> > isn't even a designed in way to make one.
>
> Ugh. Can we get the Python boys to raise their level of concern about
> that?
I looked through Python's configure script, and it appears that the
default is to build as a shared library.
> The real problem is that on systems where non-PIC code can't be used to
> build a shared library, the whole thing will not work at all. As with
> plperl, it'd be nice if we could detect this at configure time.
Python versions greater than 1.5.2 ship with the distutils module, it
can be used to detect if python was built with a shared library. Is
there anyway to detect whether non-PIC code can be used in a shared
library?
Andrew
--
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-05-13 03:50:39 | Re: bug in "create unique index" |
Previous Message | Tom Lane | 2001-05-13 03:22:58 | Re: SET variables |