 | 1 | initial version |
When is ./sage -sh NOT supposed to work? That is, where should this work in the spkg build process? My sense is that it should work almost immediately - even before Python, right? - but sometimes I get the message about it not working in the middle of a build I need to ./sage -sh in to set environment variables correctly.
An acceptable answer to this could include any other way to set the appropriate variables during a build.
| | 2 | No.2 Revision |
When is ./sage -sh NOT supposed to work? That is, where should this work in the spkg build process? My sense is that it should work almost immediately - even before Python, right? - but sometimes I get the message about it not working in the middle of a build I need to ./sage -sh in to set environment variables correctly.
I should point out that currently I have a lot of stuff built - Python, Pari, GSL, ecl, elliptic curves - but when I do what the message says (edit $SAGE_ROOT in ./sage) then I just get a message about sage-sage not existing in local/bin, which it is true, it does not.
An acceptable answer to this could include any other way to set the appropriate variables during a build.
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
