Tom Lane said: > Andrew Dunstan <[EMAIL PROTECTED]> writes: >> The last REL7_4_STABLE build the machine did had this: > >> ccache gcc -O2 -fno-strict-aliasing -g -Wall -Wmissing-prototypes >> -Wmissing-declarations -fpic -shared -Wl,-soname,libplpython.so.0 >> plpython.o -L../../../src/port -L/usr/lib/python2.2/config -ldl >> -lpthread -lutil -lm -lpython2.2 -o libplpython.so.0.0 > >> So it looks like this is what's missing: -L/usr/lib/python2.2/config >> ... I see that indeed there is libpython2.2.a in that location. > > Yeah, I had just found the same on my machine. However, what we'd > really *rather* it link to is a libpython.so someplace. The link > against libpython.a results in copying all of the python interpreter > into plpython.so. > > 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 If we want to insist on a shared lib then we should check for it as we do for plperl, shouldn't we? cheers andrew ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
