Thanks for the response! We have been involved in production 'issues'
today, sorry I didn't get back on this sooner (plus we are on Hawaiian
time). (3 hours later - the first response bounced at Verizon's outgoing
mail server, for some reason).
'openpty' is a function defined in a Python library module 'pty'. I'm
not sure how the load mechanism would work, I guess it's time for me to
'use the source!'?
BTW,
bash-2.05$ ldd /usr/local/pgsql/lib/plpython.so
libpython2.2.so => /usr/local/lib/libpython2.2.so (0x4000a000)
libc.so.6 => /lib/libc.so.6 (0x400f8000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
and,
bash-2.05$ ldd /usr/local/lib/libpython2.2.so
libc.so.6 => /lib/libc.so.6 (0x400ee000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
Doesn't seem overly helpful in this case, except to maybe eliminate an
avenue of inquiry?
Thanks again, Tom.
Chris Hall
Tom Lane wrote:
>Chris Hall <hall.cj@verizon.net> writes:
>
>
>>bash-2.05$ /usr/local/pgsql/bin/createlang plpython template1
>>ERROR: Load of file /usr/local/pgsql/lib/plpython.so failed:
>>/usr/local/lib/python2.2/config/libpython2.2.so: undefined symbol: openpty
>>createlang: language installation failed
>>
>>
>
>What shared library provides openpty() on your system? Is that library
>in the dynamic loader's search path?
>
>It might be useful to do
> ldd /usr/local/lib/python2.2/config/libpython2.2.so
>and see how the library's shared-library references get resolved.
>
> regards, tom lane
>
>
>
--
One OS to rule them all, one OS to find them,
One OS to bring them all and in the database bind them,
In the Land of Redmond, where the Shadows lie.
