After upgrding to 6.9 version I obtain
Unhandled SIGILL: An illegal instruction occurred in Sage. This probably occurred because a compiled component of Sage has a bug in it and is not properly wrapped with sig_on(), sig_off().
as response to use of float 1.2 but 12/10. works fine.
iMac (2008) Intel Core 2 Duo.
Same problem on Mac Pro 2010 with X5690 processors.
Running sage with -gdb reveals the illegal instruction is in libmpir in function __gmpf_set_d.
It is a macro actually: the function is mpf_set_d.
So anyway, my processors are the latest Nehalem. I guess the illegal instruction came with Sandy Bridge or Ivy Bridge.
Wow, that is pretty specific! Hopefully it will help... my guess is still a simple incompatibility though.
I take this as you have an upgraded Mac, right? And which version of OSX? (IMHO it's a non-standard config anyway, and you'd be best off building from source.)
So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)
sage-6.6-x86_64-Darwin-OSX_10.7_x86_64-app fails (also)
Something is broken in my system?
No, it just means that the 10.7 one is too old compared to 10.10, and the 10.10 one is built with too new a processor for your machine. So you will probably have to build from scratch. It is not so hard to do this, the main thing is to get the "command line tools" from Apple. Search this site for what that is or ask back :) but unfortunately it's very hard to provide binaries for every system.
After 6 o 7 h. compilation finishes with error on r-3.2.2.p0 (some part of R?).
Sage itself seems to work OK!!!
The log finnishes with:
make[7]: * [sysdata] Error 133
make[6]: * [all] Error 2
make[5]: * [R] Error 1
make[4]: * [R] Error 1
make[3]: * [R] Error 1
Error building R.
real 6m16.079s
user 4m7.538s
sys 0m52.003s
Error installing package r-3.2.2.p0
You may not be done compiling, though. This is a good discussion for sage-devel.
Correct, the compilation has no finished. But I have obtained a working Sage (notebook included).
Asked: 9 years ago
Seen: 1,053 times
Last updated: Nov 02 '15
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
In what sense did you upgrade? Did you download a new binary? If so, which one? What version of Mac OS do you have? Thanks!
I dowloaded the new binary (sage-6.9-x86_64-Darwin-OSX_10.10_x86_64-app.dmg 2015-10-14). Using MacOS 10.10.5 (Yosemite). In fact, I think the problem appears yet in 6.8 .
Hmm, perhaps this is similar to http://ask.sagemath.org/question/2664...
And http://ask.sagemath.org/question/7907... - but indeed the Core 2 Duo has had some problems with this in the past.
To display inline code, like
z = x*y, use backticks.To display blocks of code or error messages, skip a line above and below, and do one of the following (all give the same result):
For instance, typing
produces:
Please edit your question to do that.