[PyKDE] Undefined symbol: sipWrapperTypeName

Phil Thompson phil at riverbankcomputing.co.uk
Tue Dec 9 22:38:01 GMT 2003


On Tuesday 09 December 2003 6:41 pm, Jim Panetta wrote:
> Phil Thompson wrote:
> > On Thursday 04 December 2003 3:17 am, Jim Panetta wrote:
> >>Hi all,
> >>
> >>I'm importing a SIP-ified shared library into python.
> >>This seems to work on Windows, but not Linux.  Each of
> >>PATH, PYTHONPATH and LD_LIBRARY_PATH contain the path
> >>to libsip.so, which defines sipWrapperTypeName.
> >>( output from nm -C : 0000c444 D sipWrapperTypeName )
> >>
> >>My library is compiled with gcc version 2.95.3 with the
> >>following options:
> >>g++ -shared  <files>  -Wl,--rpath
> >>-Wl,/afs/slac/g/glast/applications/python/Python-2.2.2/@sys/lib/python2.2
> >>/site-packages
> >> -L/afs/slac/g/glast/applications/python/Python-2.2.2/@sys/lib/python2.2/
> >>site-packages -Wl,-soname -Wl,libEBFc.so.0 -o .libs/libEBFc.so.0.0.0
> >>
> >>Any ideas?
> >
> > So what actually happens?
>
> $ python -i EBFdump.py
> Traceback (most recent call last):
>    File "EBFdump.py", line 77, in ?
>      import EBF
>    File
> "/afs/slac.stanford.edu/u/ec/panetta/vol2/Online/EBF/obj/EBF.py", line
> 6, in ?
>      import libEBFc
> ImportError:
> /afs/slac.stanford.edu/u/ec/panetta/vol2/Online/EBF/obj/libEBFc.so:
> undefined symbol: sipWrapperTypeName
>
> > Are you using build.py or configure.py?
>
> Neither.  I'm not compiling SIP.
>
> > What version of SIP?
>
> $ sip -V
> 3.8 (build 109)

I can only guess that the version of the sip library the extension was linked 
against is newer than the one installed.

Phil




More information about the PyQt mailing list