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

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

I've resolved the problem with the old visual.  On rebuilding, there
was an error that libGL.so did not exist.  It did, but it was a link
to libGL.so.1.2, which did not exist.  However, libGL.so.1 did exist,
as a link to libGL.so.1.0.5336.  Pointing libGL.so to libGL.so.1 allowed
visual to build, and it runs fine again.

Does that constitute a bug in xlibmesa-gl-dev (the package which
appears to own /usr/lib/libGL.so)?

Onward to visual-3.0...  And thanks, Jonathan, for your assistance.


> On Friday 23 July 2004 03:23 pm, Jonathan Brandmeyer wrote:
> > On Fri, 2004-07-23 at 15:49, Martin Gelfand wrote:
> > > 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).
> >