[Visualpython-users] no-go with new (and old!) visual on linux

[Martin G. <mar...@co...>]

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)

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.

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?

Thanks for your attention.

-- 
Martin Gelfand

Associate Professor.............Phone: 970 491 5263
Department of Physics.............Fax: 970 491 7947
Colorado State University.......Email: ge...@la...
Fort Collins CO 80523-1875