On Tue, Jul 19, 2005 at 06:06:00PM -0500, Jim C. Nasby wrote:
> PROTECTED]:00]~/buildfarm/HEAD/pgsqlkeep.1121809875/src/pl/plpython:41%otool 
> -L libplpython.0.0.so 
> libplpython.0.0.so:
>         /System/Library/Frameworks/Python.framework/Versions/2.3/Python 
> (compatibility version 2.3.0, current version 2.3.0)
>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 71.1.3)

If that first object has something to do with Python 2.3 then we
might have found the culprit.  But how'd you get that?

> configure.log:checking Python configuration directory... 
> /opt/local/lib/python2.4/config
> configure.log:checking how to link an embedded Python application... 
> -L/opt/local/lib/python2.4/config -lpython2.4 -ldl

The above looks reasonable.

> make.log:ccache gcc -no-cpp-precomp -O2 -Wall -Wmissing-prototypes 
> -Wpointer-arith -Wendif-labels -fno-strict-aliasing -g  -bundle  plpython.o  
> -L../../../src/port -L/opt/local/lib -bundle_loader 
> ../../../src/backend/postgres -framework Python  -o libplpython.0.0.so

Hmmm...what's that "-framework Python" business?  Looks mighty
suspicious in light of the otool output.

Michael Fuhr

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to