On Mar 27, 4:55 pm, Michel <[EMAIL PROTECTED]> wrote:
> Hi Michael,
Hi Michael,
> I feel embarrassed causing so much trouble While answering your
> email I finally solved the problem
> (which was my fault of course). I turned out that I had a stray libstdc
> ++.so.6 in my home directory whic
Hi Michael,
I feel embarrassed causing so much trouble While answering your
email I finally solved the problem
(which was my fault of course). I turned out that I had a stray libstdc
++.so.6 in my home directory which somehow
Singular picked up (don't know why).
The reason why I had this str
On Mar 27, 7:03 am, Michel <[EMAIL PROTECTED]> wrote:
> "which sage" gives /usr/bin/sage which is the usual script which sets
> SAGE_ROOT (/usr/local/share/sage-2.10.4 in this case) and
> calls /usr/local/share/sage-2.10.4/local/bin/sage-sage.
>
> Things like
> env SAGE_ROOT=/usr/local/share/sa
"which sage" gives /usr/bin/sage which is the usual script which sets
SAGE_ROOT (/usr/local/share/sage-2.10.4 in this case) and
calls /usr/local/share/sage-2.10.4/local/bin/sage-sage.
Things like
env SAGE_ROOT=/usr/local/share/sage-2.10.4 /usr/local/share/
sage-2.10.4/local/bin/sage-sage -singul
On Wed, 26 Mar 2008 15:36:14 -0700, Michel <[EMAIL PROTECTED]> wrote:
>
> I have a fresh sage-2.10.4 install (compiled from source). I have done
> "make install"
> and "install_scripts".
>
> If I do "sage -singular" I get
Is the output of
which sage
the sage script that is in you SAGE_ROOT
