On Sun, Oct 25, 2015 at 3:46 PM, Volker Braun <vbraun.n...@gmail.com> wrote: > Are those the new binaries that I built with SAGE_FAT_BINARY=yes, or the > previous ones? The new md5sum is: > > $ md5 * > MD5 (sage-6.10.beta1-x86_64-Darwin-OSX_10.11-app.dmg) = > 879b8f796ffacc84a372987539a3fc4d > MD5 (sage-6.10.beta1-x86_64-Darwin-OSX_10.11.dmg) = > f5eba161c01c37aa0422519dd4f028d6 >
I have the old one. I'll try again. > > > > On Sunday, October 25, 2015 at 8:36:04 PM UTC+1, David Joyner wrote: >> >> On Sun, Oct 25, 2015 at 4:35 AM, Christian Nassau >> <nas...@nullhomotopie.de> wrote: >> > On 25.10.2015 01:03, Volker Braun wrote: >> >> >> >> I've used that ticket to build relocatable OSX 10.11 binaries and >> >> uploaded >> >> them to http://files.sagemath.org/osx/intel/index.html. They work >> >> except you >> >> can't compile stuff on top of these binaries since the library install >> >> names >> >> are still wrong. In any case feel free to test and report back... >> > >> > >> > I get a segfault on startup, probably because my (virtual) processor is >> > a >> > plain core2duo and mpir is expecting something more sophisticated: >> > >> > Program received signal SIGILL, Illegal instruction. >> > 0x000000010ac310b0 in __gmpf_set_d () >> > from >> > /Volumes/sage-6.10.beta1-x86_64-Darwin/sage/local/lib/libmpir.16.dylib >> > >> >> I might have the same issue >> >> >> jeeves:sage-6.10b1 wdj$ ./sage >> ┌────────────────────────────────────────────────────────────────────┐ >> │ SageMath Version 6.10.beta1, Release Date: 2015-10-21 │ >> │ Type "notebook()" for the browser-based notebook interface. │ >> │ Type "help()" for help. │ >> └────────────────────────────────────────────────────────────────────┘ >> ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ >> ┃ Warning: this is a prerelease version, and it may be unstable. ┃ >> ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ >> ------------------------------------------------------------------------ >> 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(). >> Sage will now terminate. >> ------------------------------------------------------------------------ >> Illegal instruction: 4 >> >> I tried sage -b as root but get the same error. My processor is a >> >> 2.66 GHz Intel Core 2 Duo >> >> >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "sage-devel" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to sage-devel+...@googlegroups.com. >> > To post to this group, send email to sage-...@googlegroups.com. >> > Visit this group at http://groups.google.com/group/sage-devel. >> > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
