mabshoff wrote: > > > On Mar 1, 8:46 am, Jaap Spies <j.sp...@hccnet.nl> wrote: >> Pat LeSmithe wrote: > > <SNIP> [...] > It would, but do the following: take a throw away Python tree and > modify the python.spkg to add -fPIC to the default flags. Take the > libpython2.5.a and turn it into a shared library: > > mabsh...@sage:/scratch/mabshoff/sage-3.4.alpha0/local/lib/python2.5/ > config$ cd foo/ > mabsh...@sage:/scratch/mabshoff/sage-3.4.alpha0/local/lib/python2.5/ > config/foo$ ar xf ../libpython2.5.a > mabsh...@sage:/scratch/mabshoff/sage-3.4.alpha0/local/lib/python2.5/ > config/foo$ gcc -shared *.o -o libpython.so > /usr/bin/ld: abstract.o: relocation R_X86_64_32 against `a local > symbol' can not be used when making a shared object; recompile with - > fPIC > abstract.o: could not read symbols: Bad value > collect2: ld returned 1 exit status > > This blows up because I was too lazy to build a libpython2.5.a with - > fPIC, but the rest should work. Then drop that libpython.so into > $SAGE_LOCAL/lib and the linker should pick it up.
This procedure will not save my experimental paraview spkg :(! 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 -~----------~----~----~----~------~----~------~--~---
