On Tue, Jul 19, 2005 at 01:54:00PM -0600, Michael Fuhr wrote:
> On Tue, Jul 19, 2005 at 02:48:52PM -0400, Tom Lane wrote:
> > "Jim C. Nasby" <[EMAIL PROTECTED]> 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"?

Oddly, no, it doesn't seem to have ldd. And the buildfarm script seems
to clean everything up even in the pgsqlkeep directories; or at least I
couldn't find a plpython.so laying around.
Jim C. Nasby, Database Consultant               [EMAIL PROTECTED] 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?


Reply via email to