[vtkusers] Python mismatch error on IRIX

[Randy Heiland]

FWIW, a follow-up.  I built from CVS, but was only successful after using the
*shared* Python lib, libpython2.2.so (the static lib always produced the
mismatch error).  Then I could use either 'python' or 'vtkpython' and
successfully import <vtkpythonlibs>.

Thanks to all who replied.

--Randy


On Jan 15,  1:35pm, Randy Heiland wrote:
> Subject: Re: [vtkusers] Python mismatch error on IRIX
> Hmm.  This leads me to ask - how was I able to do it (import VTK libs into
> Python) before?
>
> Yes, I did see mention of the 'vtkpython' while searching the VTK archives,
> however was confused since I only had 'vtkpython.py'.
>
> I'll try CVS...
>
> --Randy
>
>
> On Jan 15,  2:29pm, Andy Cedilnik wrote:
> > Subject: Re: [vtkusers] Python mismatch error on IRIX
> > Hi Randy,
> >
> > This is a "known" problem with importing C++ library (VTK) to C program
> > (Python). The solution will be available in VTK 4.2 which will be
> > released shortly (or in VTK nightly available from www.vtk.org).
> >
> > The solution looks like this. Instead of running your scripts using
> > /usr/bin/python (or whatever), you use executable from VTK called
> > vtkpython. This one should work fine.
> >
> > 			Andy
> >
> > On Wed, 2003-01-15 at 13:57, Randy Heiland wrote:
> > > After a long absence from VTK on IRIX, I've returned to try to help a
> coworker
> > > (and am remembering why I left in the first place :).  In short, I'm
> getting
> > > this error:
> > >
> > > % cd VTK/bin
> > > % python
> > > Python 2.2.2 (#1, Jan 15 2003, 07:20:16) [C] on irix646-64
> > > Type "help", "copyright", "credits" or "license" for more information.
> > > >>> from libvtkCommonPython import *
> > > Fatal Python error: Interpreter not initialized (version mismatch?)
> > > Abort (core dumped)
> > >
> > > I'm using:
> > >
> > > IRIX 6.5, 64-bit
> > > vtk40Src.tar
> > > Python2.2.2
> > >
> > > I built Python - static lib, no threads, and VTK - with just Python
> wrapping
> > > (using MIPSpro cc,CC, Version 7.30)
> > >
> > > I'm convinced I did not build VTK w/ a different Python than the one I'm
> using
> > > to execute.  Googling for this type of error, I see mention of a problem
> with
> > > threads, so my last build was threadless.  I've about run out of guesses.
> > >
> > > FWIW, here's the ldd (see, no threads):
> > > % ldd libvtkCommonPython.so
> > >         libm.so  =>      /usr/lib64/libm.so
> > >         libvtkCommon.so  =>      <path>/VTK/bin/libvtkCommon.so
> > >         libCsup.so  =>   /usr/lib64/libCsup.so
> > >         libC.so.2  =>    /usr/lib64/libC.so.2
> > >         libc.so.1  =>    /usr/lib64/libc.so.1
> > >
> > > ldd libvtkCommon.so
> > >         libm.so  =>      /usr/lib64/libm.so
> > >         libCsup.so  =>   /usr/lib64/libCsup.so
> > >         libC.so.2  =>    /usr/lib64/libC.so.2
> > >         libc.so.1  =>    /usr/lib64/libc.so.1
> >
> >-- End of excerpt from Andy Cedilnik
>
>
> _______________________________________________
> This is the private VTK discussion list.
> Please keep messages on-topic. Check the FAQ at:
<http://public.kitware.com/cgi-bin/vtkfaq>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers
>-- End of excerpt from Randy Heiland