On Thu, May 01, 2008 at 04:12:36AM -0600, Gary Furnish wrote: > > If you export SAGE_PBUILD=yes before you run make (so that it uses > pbuild from the beginning) it is necessary to link site-packages > yourself with the following command from $SAGE_ROOT: > ln -s devel/sage/build/sage/ local/lib/python/site-packages/sage
On my system the sage spkg fails to build when trying to link libcsage.so. It seems this is because it tries to link against -lpython2.5. It fails for two reasons: the right -L option isn't given (and I don't have a system-wide python 2.5 installed), and if I manually add the -L, it complains that libpython2.5.a isn't PIC. Removing the entire -lpython2.5 appears to fix things. If after that I also manually do ln -s ../../../../devel/sage/build/sage/ local/lib/python/site-packages/sage from $SAGE_ROOT, sage starts ok. One potentially strange thing is that it appears to build libcsage.so twice. Right at the start (even before the 'Building with 2 threads' notice), where it links fine, and a second time that I described above. -Willem Jan --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
