Error compiling cysignals-1.10.3 / gcc 11.2.0

85 views
Skip to first unread message

Manuel González

unread,
Sep 24, 2021, 9:52:15 PM9/24/21
to sage-devel
cysignals-1.10.3.log

jonatha...@googlemail.com

unread,
Sep 25, 2021, 4:04:21 AM9/25/21
to sage-devel

MINSIGSTKSZ is no longer a constant, which causes this problem.

Does it compile, when you add `--std=c11` to your `CFLAGS`.

E.g. do `sage -sh` and then `echo $CFLAGS` and then

run

make cysignals CFLAGS="<whatever you saw> --std=c11"

Jonathan
Manuel González schrieb am Samstag, 25. September 2021 um 03:52:15 UTC+2:

jonatha...@googlemail.com

unread,
Sep 25, 2021, 7:09:32 AM9/25/21
to sage-devel
Sorry for the wrong reference, I guess the following reference is better:


Maybe compiling cysignals without march native is also and option until this problem is resolved for cysignals.

Manuel González

unread,
Sep 25, 2021, 5:52:48 PM9/25/21
to sage-devel
Unfortunatelly it doesn't compile, exact same error

Being this an error caused by a change in glibc 2.34 I don't think there is much
to do whilst we wait for the cysignals fix, but I may be wrong,.
so any other idea is welcome

Thanks
Manuel

jonatha...@googlemail.com

unread,
Sep 28, 2021, 6:55:01 AM9/28/21
to sage-devel
I have have found a fix elsewhere and copy/pasted it in https://github.com/sagemath/cysignals/pull/151, this might already solve the issue.

Fixes this and possibly upgrading cysignals is now
Reply all
Reply to author
Forward
0 new messages