Re: [PATCHES] Patch to fix plpython on OS X - Mailing list pgsql-hackers

From Michael Fuhr
Subject Re: [PATCHES] Patch to fix plpython on OS X
Date
Msg-id 20050719195400.GA27471@winnie.fuhr.org
Whole thread Raw
In response to Re: [PATCHES] Patch to fix plpython on OS X  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Patch to fix plpython on OS X
List pgsql-hackers
On Tue, Jul 19, 2005 at 02:48:52PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <decibel@decibel.org> writes:
> > I don't think it's a version issue; cuckoo is at 2.4, platypus used to
> > be at 2.3 but I upgraded it to 2.4 to see if that was the issue, but
> > platypus kept working.
>
> Hmm ... if it's *not* a version thing then I really do want to know
> what's causing it.  Anyone have an idea why this machine is saying
> '\u80' where everyone else's python says u'\x80' ?

Is it possible that plpython.so is linked against an old version
of libpython?  I see that the error message changed a few years ago:

http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Python/exceptions.c?r1=1.44&r2=1.45
http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Python/exceptions.c?r1=1.45&r2=1.46

As I recall, Python must be configured with --enable-shared or you
don't get a shared version of libpython, so if you installed a new
Python but not a new version of libpython.*.so, then plpython.so
might be linked against an old version.

Does this machine have ldd or the equivalent?  If so, can you compare
"ldd /path/to/python" and "ldd /path/to/plpython.so"?

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: More buildfarm stuff
Next
From: "Jim C. Nasby"
Date:
Subject: Re: More buildfarm stuff