Nathann
On 4 Jul 2015 10:36 pm, "Volker Braun" <vbrau...@gmail.com> wrote:
>
> Looks like sympy wasn't installed correctly... can you look into the sympy logs? Maybe recompile if you don't remember how you got there?
I've turned in for the night (typing this on my tablet) but will get back to you as soon as I get a chance tomorrow.
On OSX I had time so ran:
```
make dist-clean
make
```
On Ubuntu:
```
make clean
make
```
If you could point out where the sympy logs would be I'll send them tomorrow before I recompile (or indeed throw any other instructions my way :)).
Vince
On 4 Jul 2015 10:36 pm, "Volker Braun" <vbrau...@gmail.com> wrote:
>
> Looks like sympy wasn't installed correctly... can you look into the sympy logs? Maybe recompile if you don't remember how you got there?I've turned in for the night (typing this on my tablet) but will get back to you as soon as I get a chance tomorrow.
On OSX I had time so ran:
```
make dist-clean
make
```On Ubuntu:
```
make clean
make
```If you could point out where the sympy logs would be I'll send them tomorrow before I recompile (or indeed throw any other instructions my way :)).
Have just rebuilt and still have the same problem.
Here is a link to the install.log file from the original build after
running `make dist-clean` (it's 196014 lines):
https://www.dropbox.com/s/obi5rj5gmp8xoux/install.log?dl=0
No sympy logs, apologies if I'm missing something...
Or the code is buggy as well :)
I guess that s and d are returned but they are uninitialized and actually contain memory addresses which are about 45 bits.
But the one in doctest/test.py keeps being there.
----------------------------------------------------------------------
sage -t --long --warn-long 29.8 src/sage/doctest/test.py # 1 doctest failed