I have tried to compile sage-6.8 (yesterday I wrote 2.6 instead of 6.8 by mistake) under osx 10.11 beta4, again without sucess.
This is the final error message: ---- ------------------------------------------------------------------------ Unhandled SIGSEGV: A segmentation fault 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. ------------------------------------------------------------------------ ./sage: line 134: 71464 Segmentation fault: 11 "$SAGE_ROOT/src/bin/sage" "$@" make[2]: *** [doc-html] Error 139 make[1]: *** [all] Error 2 real 1584m1.633s user 543m24.211s sys 61m11.615s *************************************************************** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all'): The build directory may contain configuration files and other potentially helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. make: *** [all] Error 1 ---- The entire log file is here (a 22.9 MB file): https://dl.dropboxusercontent.com/u/8293746/log-compiling-sage68-osx10.11-beta4.txt If I use ./sage, I get this message: --- Last login: Thu Aug 6 01:32:40 on ttys000 AirTeXano:~ jvarona$ cd /Applications/sage-6.8 AirTeXano:sage-6.8 jvarona$ ./sage ┌────────────────────────────────────────────────────────────────────┐ │ SageMath Version 6.8, Release Date: 2015-07-26 │ │ Type "notebook()" for the browser-based notebook interface. │ │ Type "help()" for help. │ └────────────────────────────────────────────────────────────────────┘ This looks like the first time you are running Sage. Updating various hardcoded paths... (Please wait at most a few minutes.) DO NOT INTERRUPT THIS. Done updating paths. ********************************************************************** Oops, Sage crashed. We do our best to make it stable, but... A crash report was automatically generated with the following information: - A verbatim copy of the crash traceback. - A copy of your input history during this session. - Data on your current Sage configuration. It was left in the file named: '/Users/jvarona/.sage/ipython-3.2.0/Sage_crash_report.txt' If you can email this file to the developers, the information in it will help them in understanding and correcting the problem. You can mail it to: sage-support at sage-supp...@googlegroups.com with the subject 'Sage Crash Report'. If you want to do it now, the following command will work (under Unix): mail -s 'Sage Crash Report' sage-supp...@googlegroups.com < /Users/jvarona/.sage/ipython-3.2.0/Sage_crash_report.txt To ensure accurate tracking of this issue, please file a report about it at: http://trac.sagemath.org --- And this is the Sage_crash_report.txt file (32 KB file): https://dl.dropboxusercontent.com/u/8293746/Sage_crash_report.txt -- 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.
