OS X 10.12

[crown...@gmail.com]

Does SAGE work on OS X 10.12?  I moved SageMath to my applications directory and then

────────────────────────────────────────────────────────────────────┐
│ SageMath version 7.5.1, Release Date: 2017-01-15                   │
│ Type "notebook()" for the browser-based notebook interface.        │
│ Type "help()" for help.                                            │
└────────────────────────────────────────────────────────────────────┘

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 recompi

[Dima Pasechnik]

Yes it does work on 10.12.

Could you provide the link to the binary package you tried to install?

(It might be broken...)

[Justin C. Walker]

On Mar 7, 2017, at 11:14 , Crown...@gmail.com wrote:

> Does SAGE work on OS X 10.12? I moved SageMath to my applications
> directory and then
>
> ────────────────────────────────────────────────────────────────────┐
> │ SageMath version 7.5.1, Release Date: 2017-01-15 │
> │ Type "notebook()" for the browser-based notebook interface. │
> │ Type "help()" for help. │
> └────────────────────────────────────────────────────────────────────┘

From the look of this:

>
> 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:

I'll guess that someone built the Sage system, and then you (?) moved it, as indicated.

As the message says, if you run Sage, and then move that tree somewhere else, it does what you saw: complain and stop.

When run for the first time, Sage tells you that it is "hardcoding paths", which is why you can't move it after running.

HTH

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------

[crown...@gmail.com]

I downloaded sage-7.6-OSX_10.12.3-x86_64.dmg from http://mirrors.mit.edu/sage/osx/intel/index.html

I just tried again, and I got a max recursion error:

 /Applications/SageMath/sage ; exit;
RecursionError: maximum recursion depth exceeded during compilation
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 7.6, Release Date: 2017-03-25                     │

│ Type "notebook()" for the browser-based notebook interface.        │
│ Type "help()" for help.                                            │
└────────────────────────────────────────────────────────────────────┘

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")

logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...24 completed.

[Process completed]

[John H Palmieri]

 This looks strange. It ought to look like this the first time you run Sage, and this is what happens when I download and install from that file:

Rewriting paths for your new installation directory
===================================================

This might take a few minutes but only has to be done once.

(and then hundreds of lines about patching files)


If you didn't see that, something is going wrong. Can you describe exactly what you did? Maybe you should delete the old dmg file and redownload it, in case it was corrupted somehow.

--
John

[J. Friedman]

I downloaded the dmg file, moved the sagemath directory to Applications, then double clicked on sage. 

I also tried it through home-brew and also got an error (below). Has anyone done a fresh install with an apple running the latest version of OS X?

The easiest thing for me to do was download linux in a virtual box and run it sage off Linux, however I can’t connect to the sage server (even though I can successfully SSH to the virtual machine). Any suggestions. 

RecursionError: maximum recursion depth exceeded during compilation

┌────────────────────────────────────────────────────────────────────┐

│ SageMath version 7.5.1, Release Date: 2017-01-15                   │

│ Type "notebook()" for the browser-based notebook interface.        │

│ Type "help()" for help.                                            │

└────────────────────────────────────────────────────────────────────┘

ERROR:  The Sage installation tree has moved

from /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma

  to /Applications/SageMath-7.5.1.app/Contents/Resources/sage

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")

snapdragon:~ joshua$ 

--
You received this message because you are subscribed to a topic in the Google Groups "sage-support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-support/MRhTG336Fr0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-support...@googlegroups.com.
To post to this group, send email to sage-s...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[Volker Braun]

There is supposed to be a script called "relocate-once.py" next to the sage launch script that is missing for you. It runs automatically when you start sage for the first time and then delets itself. I don't know how you lost that file...

[John H Palmieri]

Is is also possible that a homebrew installation is interfering? I have seen claims that it can interfere with building Sage from scratch, but I don't see why it would cause problems with installing from a pre-built binary.

  John

[Volker Braun]

On Saturday, April 1, 2017 at 1:25:28 AM UTC+2, John H Palmieri wrote:

Is is also possible that a homebrew installation is interfering?

Its definitely not the case here, the path /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma means that the relocate-once.py script has never been run for whatever reason.

In general, I agree that its unlikely that homebrew would interfere with pre-built binaries.

[Dima Pasechnik]

Perhaps an antivirus or some similar protection thing kicked in?

Am I recalling right that default OSX 10.12 security settings should not be a problem?

[John H Palmieri]

On Friday, March 31, 2017 at 3:36:11 PM UTC-7, Crown...@gmail.com wrote:

I downloaded the dmg file, moved the sagemath directory to Applications, then double clicked on sage. 

I also tried it through home-brew and also got an error (below). Has anyone done a fresh install with an apple running the latest version of OS X?

Yes, I did this before my first response in this thread, to make sure it works for me. I downloaded both the dmg and the tar.bz2 files, installed from each, and it worked fine. I also build from source regularly on OS X 10.12.4.

 

[crown...@gmail.com]

I use Anaconda python 3. Does your Move script use python 2?

[Volker Braun]

We most likely require at this point that the system "python" command is python2. Which is also what pep 394 recommends.

[Dima Pasechnik]

hmm, perhaps the script should check that python==python2 and show a warning, at least...

[Ruben Zilibowitz]

Same with me on OS X 10.12.4. And I'm getting the same error as you with installation.

[J. Friedman]

I moved python2 ahead in my $PATH, I found he relocate script, it seemed to run, but then errors running sage:

Traceback (most recent call last):

  File "/Users/joshua/sage/SageMath/src/bin/sage-ipython", line 7, in <module>

    from sage.repl.interpreter import SageTerminalApp

  File "/Users/joshua/sage/SageMath/local/lib/python2.7/site-packages/sage/repl/interpreter.py", line 107, in <module>

    from sage.repl.preparse import preparse

  File "/Users/joshua/sage/SageMath/local/lib/python2.7/site-packages/sage/repl/preparse.py", line 223, in <module>

    import six

  File "/Users/joshua/sage/SageMath/local/lib/python2.7/site-packages/six.py", line 27, in <module>

    import operator

ImportError: dlopen(/Users/joshua/sage/SageMath/local/lib/python2.7/lib-dynload/operator.so, 2): Symbol not found: __PyUnicodeUCS4_AsDefaultEncodedString

  Referenced from: /Users/joshua/sage/SageMath/local/lib/python2.7/lib-dynload/operator.so

  Expected in: flat namespace

 in /Users/joshua/sage/SageMath/local/lib/python2.7/lib-dynload/operator.so

snapdragon:SageMath joshua$ 

[J. Friedman]

I got it to work.

So I think the problem is python 3, with Anaconda. I logged in under another user name that uses Apple’s Python 2. And installed Sage. Then, I can run it from my python 3 account. Perhaps your scripts should search out Python 2 when there are multiple versions installed.

[Volker Braun]

This is presumably fixed in 22608 by removing PYTHONPATH/PYTHONHOME from sage-env.