[vtkusers] Re: compiling vtk nightly or 4.0 with Python on Solaris 2.7

[Dave Reed]

The problem appears to be that cmak1.4.3 didn't include the -G flag
that gcc (at least gcc 2.95.3 on Solaris) requires to link
properly. Once I added that, it worked.

Thanks,
Dave


> I compiled vtk nightly (July 15)  with Python2.2 successfully on Solaris 
> 2.7,
> I was using Sun compiler, though. Anyway, I attached my CMakeCache.txt
> file for your reference. I used cvs CMake (Again, July 15).
> 
> Hua
> 
> Dave Reed wrote:
> 
> >I know there was a thread about Python support on Solaris recently and
> >I've reread it, but I still can't get it to work now. I used to have
> >Python working on Solaris, but we've since installed a newer version
> >of Python and I can't seem to get it to work now.
> >
> >I get lots of errors like this while compiling:
> >
> >PyEval_RestoreThread                0x2530      /usr/local/lib/python2.2/config/libpython2.2.a(fileobject.o)
> >PyEval_RestoreThread                0x25ac      /usr/local/lib/python2.2/config/libpython2.2.a(fileobject.o)
> >
> >and it finally stops with:
> >
> >ld: fatal: relocations remain against allocatable but non-writable sections
> >collect2: ld returned 1 exit status
> >make[3]: *** [/tmp/VTK/bin/libvtkCommonPython.so] Error 1
> >make[2]: *** [default_target] Error 2
> >make[1]: *** [default_target_Common] Error 2
> >make: *** [default_target] Error 2
> >
> >I've tried both with shared libraries turned on and off, but it still
> >doesn't work. Can anyone with VTK compiled with Python support on
> >Solaris share their CMakeCache.txt file so I can see what settings I
> >might be missing.
> >
> >This is with gcc 2.95.3 which is what I previously used to compile
> >both Python and VTK. I also updated to cmake 1.4 which appeared to be
> >necessary to use the nightly version.
> >
> >Thanks,
> >Dave

<CMakeCache.txt file snipped>

Dave