On 3/28/07, Jonathan William Bober <[EMAIL PROTECTED]> wrote:
>
> Hi all. I just upgraded (by running sage -upgrade) and I am having the
> problem shown down below.
>
> Some things that I have tried include running sage with the command
>
> LD_LIBRARY_PATH="/home/bober/sage-2.3/local/lib/"
> SAGE_ROOT="/home/bober/sage-2.3/" ./sage
>
Hi Jonathan,
You should try erasing SAGE_ROOT/devel/sage-main and try reinstalling
the sage-2.4.1.2 package.
Did anyone have any luck upgrading their *branches* without this
problem? The above works wonderfully if you only care about sage-main,
but if you upgrade your branch and try to build it, you get back to
square one. This is Very Annoying.
>/home/bober/sage-2.3/local/lib/python2.5/site-packages/sage/all.py in
<module>()
43 del _l
44 except KeyError:
---> 45 raise RuntimeError, "To use the SAGE libraries, set the
environment variable SAGE_ROOT to the SAGE build directory and
LD_LIBRARY_PATH to $SAGE_ROOT/local/lib"
46
47
Incidentally, if you ignore the KeyError by commenting the
RunTimeError in all.py (around line 44), this works fine.
didier
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
