HI all,
I’ve installed python 2.3 on a SuSE 9.2 box running gcc 3.3.4. I tried installing the wxPython binary RPM (wxPythonGTK2-py2.3-2.5.2.8-RH9.i386.rpm) but ran into a undefined reference for XineramalsActive in libwx_gtk2ud_core-2.5.so.2. Looking on the lists, I’ve seen people with similar problems have been told to try building from source, which seems to have solved their problems. So I took that route myself (wxPythonGTK2-py2.3-2.5.2.8-1.src.rpm), but unfortuntely I’m now getting an undefined symbol to wxCYAN from core.so
E.g.:
__Python 2.3.4 (#1, Oct 5 2004, 00:26:51)
[GCC 3.3.4 (pre 3.3.5 20040809)] on linux2
Type “help”, “copyright”, “credits” or “license” for more information.
import wx
Traceback (most recent call last):
File “”, line 1, in ?
File “/usr/lib/python2.3/site-packages/wx/init.py”, line 42, in ?
from wx._core import *
File “/usr/lib/python2.3/site-packages/wx/_core.py”, line 4, in ?
import core
ImportError: /usr/lib/python2.3/site-packages/wx/core.so: undefined symbol: wxCYAN
__
I’ve figured I’d screwed something up in the build, so I decided to try installing the same source on a SuSE 9.0 box running GCC 3.3.1 and python 2.3+. Which worked a-ok. I’ve noticed that the install that worked uses python 2.3+ (#1, Oct 2 2003, 23:03:59), and the one that fails uses 2.3.4 (as you can see above). Could this be a problem? Are there any known incompatiblities?
Also maybe I should take a step back and see why the RPM didn’t work. Has anyone tried to get this going on SuSE 9.2?
For the record, I've discovered that this issue is because on RH9 the libXinerama library is only available as a static library whereas on newer systems it is a shared library. So my guess is that because of this something extra is getting linked in that uses and external XineramalsActive symbol that is not found on the other systems because of the difference in the available libs.
Looking on the lists, I've seen people with similar problems have been told to try building from source, which seems to have solved their problems. So I took that route myself (_wxPythonGTK2-py2.3-2.5.2.8-1.src.rpm_ <http://mesh.dl.sourceforge.net/sourceforge/wxpython/wxPythonGTK2-py2.3-2.5.2.8-1.src.rpm>\), but unfortuntely I'm now getting an undefined symbol to wxCYAN from _core_.so
E.g.:
*/Python 2.3.4 (#1, Oct 5 2004, 00:26:51) /
[GCC 3.3.4 (pre 3.3.5 20040809)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import wx
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.3/site-packages/wx/__init__.py", line 42, in ?
from wx._core import *
File "/usr/lib/python2.3/site-packages/wx/_core.py", line 4, in ?
import _core_
ImportError: /usr/lib/python2.3/site-packages/wx/_core_.so: undefined symbol: wxCYAN
>>> *
Run "ldd /usr/lib/python2.3/site-packages/wx/_core_.so" to see if it is loading the wx dynamic libraries that you built and installed, or if it is loading some other set that may already be loaded on the system.
I've figured I'd screwed something up in the build, so I decided to try installing the same source on a SuSE 9.0 box running GCC 3.3.1 and python 2.3+. Which worked a-ok. I've noticed that the install that worked uses python 2.3+ (#1, Oct 2 2003, 23:03:59), and the one that fails uses 2.3.4 (as you can see above). Could this be a problem? Are there any known incompatiblities?
Differences in Python shouldn't matter at the level of the error you are getting.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I tried running the ldd, and found that core.so just included some central Linux libraries, like libgcc, libpthread, etc, but no python libraries. Not good. Looking further at the build logs to see what happened, I exonerated python, because I think the install of SuSE may of been duff. I’ve played about with this a bit, found a few screw-ups and rebuilt python. And it has all worked fine.
Thanks for the help!
Brian
···
On Thu, 2004-10-21 at 20:16, Robin Dunn wrote:
*Brian Reynolds wrote:
> HI all,
> > I've installed python 2.3 on a SuSE 9.2 box running gcc 3.3.4. I tried > installing the wxPython binary RPM > (_wxPythonGTK2-py2.3-2.5.2.8-RH9.i386.rpm_ > <*[http://mesh.dl.sourceforge.net/sourceforge/wxpython/wxPythonGTK2-py2.3-2.5.2.8-RH9.i386.rpm](http://mesh.dl.sourceforge.net/sourceforge/wxpython/wxPythonGTK2-py2.3-2.5.2.8-RH9.i386.rpm)
>) > but ran into a undefined reference for XineramalsActive in > libwx_gtk2ud_core-2.5.so.2. For the record, I've discovered that this issue is because on RH9 the libXinerama library is only available as a static library whereas on newer systems it is a shared library. So my guess is that because of this something extra is getting linked in that uses and external XineramalsActive symbol that is not found on the other systems because of the difference in the available libs.
> Looking on the lists, I've seen people with > similar problems have been told to try building from source, which seems > to have solved their problems. So I took that route myself > (_wxPythonGTK2-py2.3-2.5.2.8-1.src.rpm_ > <[http://mesh.dl.sourceforge.net/sourceforge/wxpython/wxPythonGTK2-py2.3-2.5.2.8-1.src.rpm](http://mesh.dl.sourceforge.net/sourceforge/wxpython/wxPythonGTK2-py2.3-2.5.2.8-1.src.rpm)
>), > but unfortuntely I'm now getting an undefined symbol to wxCYAN from > _core_.so
> > E.g.:
> */Python 2.3.4 (#1, Oct 5 2004, 00:26:51) /
> [GCC 3.3.4 (pre 3.3.5 20040809)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import wx
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/lib/python2.3/site-packages/wx/__init__.py", line 42, in ?
> from wx._core import *
> File "/usr/lib/python2.3/site-packages/wx/_core.py", line 4, in ?
> import _core_
> ImportError: /usr/lib/python2.3/site-packages/wx/_core_.so: undefined > symbol: wxCYAN
> >>> *
Run "ldd /usr/lib/python2.3/site-packages/wx/_core_.so" to see if it is loading the wx dynamic libraries that you built and installed, or if it is loading some other set that may already be loaded on the system.
> > I've figured I'd screwed something up in the build, so I decided to try > installing the same source on a SuSE 9.0 box running GCC 3.3.1 and > python 2.3+. Which worked a-ok. I've noticed that the install that > worked uses python 2.3+ (#1, Oct 2 2003, 23:03:59), and the one that > fails uses 2.3.4 (as you can see above). Could this be a problem? Are > there any known incompatiblities?
Differences in Python shouldn't matter at the level of the error you are getting.