Ask Your Question

Installation problem on Mac OSX

asked 2012-11-29 01:31:15 -0500

John Frank gravatar image

updated 2012-11-29 16:50:54 -0500

benjaminfjones gravatar image

I downloaded sage-5.4.1-OSX-64bit-10.8-x86_64-Darwin.dmg and double-clicked it.

I can find README.txt and folder named "sage"

In README.txt, I can find the following:

1) Download the dmg somewhere and double click on it.

2) Drag the sage folder somewhere, e.g., /Applications

3) Use finder to visit the sage folder you just copied it and double click on the "sage" icon.

4) Select to run it with "Terminal":

5) Sage should pop up in a window.

6) For the graphical notebook, type notebook() You might have to open Firefox or Safari (your choice) to the URL http://localhost:8000 to use Sage on your computer.

I did from step 1) to step 4) and I got this message from terminal without sage pop-up:

Last login: Thu Nov 29 22:25:09 on ttys000
/Applications/sage/sage ; exit;
aca89a95:~ user$ /Applications/sage/sage ; exit;
| Sage Version 5.4.1, Release Date: 2012-11-15                       |
| Type "notebook()" for the browser-based notebook interface.        |
| Type "help()" for help.                                            |
/Applications/sage/spkg/bin/sage: line 283:   439 Segmentation fault: 11  sage-location

[Process completed]

What does this mean?

edit retag flag offensive close merge delete


You have a segmentation fault there. Do you actually have a 64bit installation of Mac OSX?

ppurka gravatar imageppurka ( 2012-11-29 03:13:49 -0500 )edit

My processor is Intel Core 2 duo. It's a 64-bit according to apple website here:

John Frank gravatar imageJohn Frank ( 2012-11-29 03:35:52 -0500 )edit

But do you have OS X 10.8?

kcrisman gravatar imagekcrisman ( 2012-11-29 03:45:47 -0500 )edit

You may also want to try the app version, though presumably it would have the same problem.

kcrisman gravatar imagekcrisman ( 2012-11-29 03:46:31 -0500 )edit

And I've heard that some of Apple's 64-bit ones are not "real" 64-bit... it would depend on what processor this was compiled on (the binary) and likely it was a newer computer.

kcrisman gravatar imagekcrisman ( 2012-11-29 03:47:20 -0500 )edit

2 answers

Sort by ยป oldest newest most voted

answered 2012-11-29 20:43:07 -0500

updated 2012-11-30 01:53:58 -0500

this Apple's link is misleading. Type of processor alone does not describe the "bitness" of the OS. E.g. Core 2 Duo Macbook Pro can well be running 32-bit OSX 10.6. To find this out exactly, click "Apple"->About this Mac->More Info->Software. You will see something like the following:

System Software Overview:

System Version: Mac OS X 10.6.8 (10K549)
Kernel Version: Darwin 10.8.0
Boot Volume:    MAC
Boot Mode:  Normal
Computer Name:  XXXXXXXXXX
User Name:  xxxxx
Secure Virtual Memory:  Enabled
64-bit Kernel and Extensions:   No
Time since boot:    21 days 2:59'

Note the line " 64-bit Kernel and Extensions: No". So this is a 32-bit system. Even though it is Core 2 Duo:

Hardware Overview:

Model Name: MacBook Pro
Model Identifier:   MacBookPro5,5
Processor Name: Intel Core 2 Duo
Processor Speed:    2.26 GHz
Number Of Processors:   1
Total Number Of Cores:  2
L2 Cache:   3 MB
Memory: 4 GB
Bus Speed:  1.07 GHz
Boot ROM Version:   MBP55.00AC.B03
SMC Version (system):   1.47f2
Serial Number (system): XXXXXXXXXX
Sudden Motion Sensor:
State:  Enabled

Some systems can be booted into 32-bit as well as into 64-bit modes using certain key combinations. See

edit flag offensive delete link more


Is there another binary the original poster could try, e.g. would the 10.6 binary work? Now that Xcode is a little more annoying to get hold of, building from source would be a second option.

kcrisman gravatar imagekcrisman ( 2012-11-30 02:00:13 -0500 )edit

answered 2012-11-30 04:49:48 -0500

Stefan gravatar image

I ran into the same problem. Turns out I downloaded the version for OS X 10.8 while I'm running 10.7. The


binary works just fine for me.

Incidentally, when did the binaries become dependent on the OS version? That's just annoying.

edit flag offensive delete link more


Look up the sage-support or sage-devel mailing list. There are changes in the OS level for every new version of Mac. So, you need to have these different binaries.

ppurka gravatar imageppurka ( 2012-11-30 07:49:36 -0500 )edit

Yes, it's always been this way. This is because Sage is highly dependent on very finicky low-level components that really do change from version to version as more stuff becomes possible on a processor, as well as some high-level stuff in the OS X business.

kcrisman gravatar imagekcrisman ( 2012-11-30 07:58:37 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2012-11-29 01:31:15 -0500

Seen: 1,455 times

Last updated: Nov 30 '12