On 2016-01-16 21:47, Buck Evan wrote:
It passed on subsequent `make`.
Then it might be a hardware problem. I suggest you run memtest on your
system to check for that.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gr
It passed on subsequent `make`.
It's good enough for now, for me.
Yes it's a Debian (Ubuntu 14.04.3).
On Saturday, January 16, 2016 at 11:41:57 AM UTC-8, Jeroen Demeyer wrote:
>
> On 2016-01-16 20:15, Buck Evan wrote:
> > The cause seems to be gcc segfaulting during tests of cython
> compilat
On 2016-01-16 20:15, Buck Evan wrote:
The cause seems to be gcc segfaulting during tests of cython compilation.
A broken GCC? Let me guess... Debian?
You can rebuild Sage with the environment variable
SAGE_INSTALL_GCC=yes
That will install a properly working GCC.
--
You received this message
Should I not attempt to build with testing? I've exported SAGE_CHECK=yes`,
which is mentioned in the README and looked like a good idea.
The cause seems to be gcc segfaulting during tests of cython compilation.
```
[1/1] Cythonizing
/home/buck/trees/mine/sage/local/var/tmp/sage/build/cython-0.2
