# problem installing sage on mac os x 10.11.5 [closed]

I am running a mac os x 10.11.5 and would like to use sage locally.

1) I first tried to install from source code. I checked that all the prerequisites were satisfied, then proceeded to download the sources, follow the steps and 'make'. it took some 10 hours; unfortunately when it finished it said it did not compile successfully.

2) so i removed the source folder from step 1, and tried the installation from binaries. I downloaded the sage-7.2-OSX_10.11.4-x86_64.dmg , then paste the folder SageMath into /Applications. When opening the sage executable, I get this error message:

```
ERROR: The Sage installation tree has moved from /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma to /Applications/SageMath This is not supported, and Sage will not work. To install Sage from a binary package: (....)
1. Open the .tar.bz2 archive (or .dmg on OSX)
2. Move the SageMath folder/app to where you want it to be. You can
also rename the directory now.
3. Start sage for the first time. This will then automatically patch
paths in binaries.
After starting Sage for the first time you cannot change the
installation any more. To install Sage elsewhere, start over from the
binary package. Or recompile Sage from scratch in the new location
("make distclean && make") here
```

Maybe this thread is related, but I didn't understand what's going on. I tried the `csrutil disable`

(after step 2), but nothing changed.

i've installed Homebrew and Anaconda; here it says that Anaconda could be causing the problem and that 'removing all traces' would solve the problem. what does that mean? thanks

'Removing all traces' means full uninstallation. Instructions for uninstalling Anaconda are down a couple small paragraphs from http://conda.pydata.org/docs/install/...

SageMath still uses Python 2.7 and your installation of Anaconda may be interfering.

@paulmasson YES, that worked, thanks!!! Now there was another trouble with the default settings of the terminal, but the solution is here (should make sure that the box in front of "Set locale environment variables on startup" in terminal preference-advanced is unchecked).