On 08.11.2015 19:42, Volker Braun wrote:
Can somebody debug where the sigill is coming from? Use gdb to narrow
down the library? (e.g. sage -f gdb and then run sage -gdb as root on OSX)
I cannot test the 6.9 on my system (without rebooting with disabled
security). But the current sage-6.10.beta1-x86_64-Darwin (with md5sum =
f5eba161c01c37aa0422519dd4f028d6) also has problems, even though it has
presumably been built with SAGE_FAT_BINARY=yes
Program received signal SIGILL, Illegal instruction.
0x000000010ab1e0b0 in __gmpf_set_d ()
from
/Volumes/sage-6.10.beta1-x86_64-Darwin/sage/local/lib/libmpir.16.dylib
On my system, I get this from the mpir platform detection code:
el-capitan:mpir-2.7.0 cn$ /bin/sh ./configfsf.guess
x86_64-apple-darwin15.0.0
el-capitan:mpir-2.7.0 cn$ /bin/sh ./config.guess
core2-apple-darwin15.0.0
The first is what's used in SAGE_FAT_BINARY=yes, the 2nd gives a working
configuration for me. Maybe we should force configfsf.guess to return
"core2" also... ?
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
