On Saturday 08 September 2007 17:49, mabshoff wrote: > Executive Summary: SCons somehow gets its LD_LIBRARY_PATH or env in > general wrong and ends up linking against the gmp 4.2.1 provided by > Debian. Somehow the compiler gets it all wrong and *boom* > > How to fix: Fix SCons *ducks* - a short term solution seems to be to > source local/sage/env before building sage-2.8.4.spkg.
This confuses me. How is source'ing local/sage/env any different from what normally happens? Isn't that always source'd once you get into the internals of sage batch files? So, I thought I could answer that question myself: In local/bin/sage-build we call local/bin/sage-env with-out source, but inside of local/bin/sage-env, we say you must: """ # You must source this; see below! """ Thus, I'm thinking that line 45 of sage-build needs 'source ' at the front, but I'm too close to my bed-time to actually go test that myself. I believe that autoconf might have not cared so much about things like this because the --prefix option got set which essentially rewrote the environment on it's own. -- Joel --~--~---------~--~----~------------~-------~--~----~ 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
