Thanks for the bug report about strip_automount_prefix. Please try the attached sage-test.
On 6/4/07, Michel <[EMAIL PROTECTED]> wrote:
>
> I am working on my chroot jail but this time I am stuck. Doctests fail
> because SAGE cannot start the standard interfaces. Here is a typical
> exception.
> In [6]: maxima.interact()
> ---------------------------------------------------------------------------
> <type 'exceptions.RuntimeError'> Traceback (most recent call
> last)
> ...................
> <type 'exceptions.RuntimeError'>: Unable to start maxima because the
> command 'maxima -p "//usr/local/sage/local/bin/sage-maxima.lisp"'
> failed.
>
> maxima.console() works fine. Also the indicated command maxima -p "//
> usr/local/sage/local/bin/sage-maxima.lisp" works fine at the bash
> prompt (I have
> done install-scripts).
>
> Does anybody recognize this situation? In particular I am very worried
> that my
> prompt is In [x]: and not sage:... What could possibly cause this?
(1) Maybe you should try building from source? You're going to want
to have a compiler in the chroot anyways, so %sagex will work,
upgrades will work, etc.
(2) What do typing
!usr/local/sage/local/bin/sage-maxima.lisp
at the SAGE prompt do?
William
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---
sage-test
Description: Binary data
