Pat LeSmithe wrote: > > Hello, > > In building the experimental ParaView package, > > http://trac.sagemath.org/sage_trac/ticket/5279 , > > on a x86_64 Fedora 9 machine with the corresponding binary distribution > of Sage 3.2.3, I got this error: > > /usr/bin/ld: > /home/qed777/apps/sage/sage-3.2.3-Fedora_release_9-x86_64-Linux/local/lib/python2.5/config/libpython2.5.a(abstract.o): > relocation R_X86_64_32 against `a local symbol' can not be used when > making a shared object; recompile with -fPIC > /home/qed777/apps/sage/sage-3.2.3-Fedora_release_9-x86_64-Linux/local/lib/python2.5/config/libpython2.5.a: > could not read symbols: Bad value > collect2: ld returned 1 exit status > make[2]: *** [bin/libvtkPVPythonInterpretor.so] Error 1 > make[1]: *** > [Utilities/VTKPythonWrapping/Executable/CMakeFiles/vtkPVPythonInterpretor.dir/all] > Error 2 > make: *** [all] Error 2 > Error building ParaView . >
I've seen this when I tried to build paraview on sage.math. I'm sorry but I don't have an other 64k machine to test this. > Subsequent attempts end with the same error but occasionally when > linking one of ParaView's other Python-related shared libraries. (The > latter behavior may stem from "make -j 2", but I'm not sure.) > > This seems to be an example of a known AMD64 quirk: > > http://mail.python.org/pipermail/python-bugs-list/2006-October/035809.html . > > Is this happening because the Sage distribution includes libpython2.5.a > but not lipython2.5.so? Or is it because some flags, such as "-fPIC," > were [intentionally] omitted when building the static library? (If it > matters, I've already added "-fPIC" to the Paraview build flags.) > Either way, can/should I reconfigure the build to link to the system's > (i.e., not Sage's) Python library? > This will not work I think. > Also, although I haven't built the experimental VTK spkg, this seems to > suggest I'd have a similar problem with it. The experimental vtk-5.2.1.spkg builds on sage.math ubuntu-8.04 64k. I've previously built the > same versions of VTK and ParaView outside of Sage without incident. > Interestingly, Kitware's binary installation of ParaView includes both > libpython2.5.a and libpython2.5-pic.a, as well as a broken link to a > missing libpython2.5.so, but it runs fine. > Can you try to configure manually with ccmake and see what happens? Jaap --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
