The problem seems also to be compiler related :
Somebody recently installed SAGE on our (scientific Linux 6.0 ) cluster
but using a more recent gcc version 4.6.0 instead of 4.4.4 which I used for
the cluster install. (since this is standart there)
The glibc version there is still 2.12.
Doing so
we currently use.
>
>
> SWO = strict weak order
>
> On Thursday, April 4, 2013 5:08:36 PM UTC+1, FalkRichter wrote:I can
> reproduce the SIGSEGV example given on that page.
>
> But I must confess that I'm unable to install the burcin pynac patches.
>
>
>
>
> SWO = strict weak order
>
> On Thursday, April 4, 2013 5:08:36 PM UTC+1, FalkRichter wrote:I can
> reproduce the SIGSEGV example given on that page.
>
> But I must confess that I'm unable to install the burcin pynac patches.
>
>
&
for patching
2 out of 2 hunks FAILED -- saving rejects to file ginac/symbol.cpp.rej
unable to find 'ginac/symbol.h' for patching
2 out of 2 hunks FAILED -- saving rejects to file ginac/symbol.h.rej
abandon : patch failed to apply
On Thursday, 4 April 2013 16:09:55 UTC+2
Thanks for fast reply. I will investigate this.
On Thursday, 4 April 2013 16:09:55 UTC+2, Volker Braun wrote:
> Most likely this is http://trac.sagemath.org/9880
>
>
> On Thursday, April 4, 2013 2:52:05 PM UTC+1, FalkRichter wrote:
> No symbol table info available.
> #1
Hi,
sage-5.8, install from source on Ubuntu10.04 LT.
the SIGSEGV has been reproduced on a Scientifuc Linux node as well.
Unfortunately I cannot not isolate it. It occurs in the middle of
the run after doing similar things a thousand times before.
Probably caused in one of the libraries used for
