From: Jonathan B. <jbr...@ea...> - 2004-07-23 21:23:53
|
On Fri, 2004-07-23 at 15:49, Martin Gelfand wrote: > I am running Debian testing, but got boost-python-dev and dependencies > from unstable (since only unstable has boost 1.31 at this time). > > Compilation of visual-3.0 seemed to go fine. I used > PYTHON=/usr/bin/python ./configure --prefix=/usr/local > (/usr/bin/python is a link to python2.3, and I want all locally built > software in /usr/local) /usr/local is configure's default prefix, and so long as /usr/bin/python is the first Python named 'python' in your PATH, that is the default as well. > Importing visual in a python2.3 shell goes OK, but I get a segfault on > trying to do anything that generates a display on-screen. I see a display > window appear, then immediately close. Simply instantiating a display > (e.g. firstdisplay=visual.display()) does not throw a segfault. visual.display has "initialize on first use" semantics, and merely instantiating one isn't enough to constitute 'use'; you have to also instantiate a rendered object. I'm using visual 3.0 on Debian Sid right now, without any problems. Can you please run the following to get a backtrace?: gdb python [displays some stuff and gives you the (gdb) prompt] (gdb) run [displays more stuff and gives you the python prompt] >>> from visual import * >>> import sys >>> sys.path.append( ... "/usr/local/lib/python2.3/site-packages/visual/demos") ... >>> import stars [ This will attempt to run the stock "stars" demo program ] [ When (if) it crashes, control will return to gdb with the (gdb) prompt.] (gdb) bt Please send me the output of the last command. Also, to partially rule out general OpenGL problems, please see if glxgears runs. Are you by chance using the R200 DRI driver? > What's worse, my old visual setup (python2.2, visual-2.1.9) no longer > works: > Python 2.2.3+ (#1, Jun 20 2004, 13:32:48) > [GCC 3.3.4 (Debian)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import visual > Visual-2003-10-05 > Traceback (most recent call last): > File "<stdin>", line 1, in ? > File "/usr/local/lib/python2.2/site-packages/visual/__init__.py", line 17, > in ? > import cvisual > ImportError: /usr/local/lib/python2.2/site-packages/cvisualmodule.so: > undefined symbol: __pure_virtual > > I don't see how this could be the fault of installing the new visual--could > it have come about due to an upgrade of python2.2 since I built that > version of visual? I don't know for certain what this could be. The only place that I can find this symbol on my system is in libgcc.a from GCC 2.95. Try rebuilding VPython 2.1.9 with the current compiler. (you will have to specify PYTHON=python2.2 to build against Python 2.2 since `python` is 2.3). -Jonathan |