-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meta-ticket: support macOS 11 Big Sur #30651
Comments
This comment has been minimized.
This comment has been minimized.
comment:3
I'm trying to compile sage-9.2.rc0 on big sur with xcode 12.0.1. I ran (see the openblas attachment). After trying lots of things such as
the compilation of However, Sage did start and crash with this error:
(for the rest, see the error-in-start attachment). It looks like Sage's Python doesn't work, right? Wrong:
In case it's any use, here is what homebrew claims it has installed:
|
comment:4
I've actually gotten this to build for me without patching Sage in any way, just building 9.2.rc0. Homebrew setup:
Then I used the command
after which
Maybe because |
comment:5
Replying to @jhpalmieri:
I could try that, but it won't work because our |
comment:6
mpir is basically not developed any more (for the time being at least), so we should not use it. What is the value of MACOSX_DEPLOYMENT_TARGET used in this build? I would not be surprised if there is an incompatibility barrier between macOS 10 and macOS 11. |
comment:7
Replying to @wdjoyner:
David, could you please replace this 10-screen comment by an attachement? |
Attachment: openblas-tail.txt openblas error |
Attachment: error-in-start.txt error in start |
comment:8
Replying to @dimpase:
It's a standard package, so I'm confused about what the alternatives are. Anyway, I hacked the spkg-install.in script for
and
I haven't changed Sage, so it's whatever gets set in sage-env: 10.9, I think. |
comment:9
Replying to @jhpalmieri:
One can choose between gmp and mpir. Both are standard, but only one is needed. Use the configure flag Likewise, one can choose between ATLAS and OpenBLAS, and both are standard. Use In that case #30350 proposes to remove ATLAS. |
comment:10
Sorry, I led us on a bit of a wild goose chase for the past few comments. Back in comment:4, I said the right thing:
But then (maybe I was tired or distracted), I started building Sage's |
comment:11
Replying to @jhpalmieri:
Just a quick remark - |
comment:12
Right. Since for me at least, Sage doesn't successfully detect the presence of the system Python on Big Sur, it always builds its own, so |
comment:13
Replying to @jhpalmieri:
Is this because of dependencies of the |
comment:14
Replying to @jhpalmieri:
...
This configure command followed by make gave me a functioning sage, so R didn't compile but I don't use it. |
comment:15
Replying to @mkoeppe:
Yes, sqlite is not successfully detected. I'll try turning that dependency off. |
comment:16
Sage built using the system Python after modifying the dependencies to avoid sqlite. I used
Unfortunately the documentation won't build and many doctests fail , in both cases with a bus error. For example:
|
comment:17
Replying to @jhpalmieri:
They cannot be, and are not, "installed together" - Default |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:22
I am having problems building
|
comment:23
Try doing |
This comment has been minimized.
This comment has been minimized.
comment:48
Replying to @jhpalmieri:
I opened #31135 for this. |
This comment has been minimized.
This comment has been minimized.
comment:50
I opened an issue with |
comment:51
Replying to @jhpalmieri:
Should be fixed in |
comment:52
I found a patch for gfortran on Intel Macs at I'll try to open a pull request tomorrow with Homebrew to see if they can patch GCC. That should hopefully fix all Fortran issues until GCC 11 comes out. |
comment:53
I noticed this morning that homebrew had updated their gcc. With the newest gcc formula you still need MACOSX_DEPLOYMENT_TARGET=11.0 make scipy in order for scipy to build, but now if you do MACOSX_DEPLOYMENT_TARGET=11.0 ./sage -t src/sage/misc/inline_fortran.py then the tests all pass. |
comment:54
Replying to @jhpalmieri:
We will have to backport the fix because numpy 1.20 has dropped support for Python 3.6, which I think we want to continue supporting in Sage 9.3 |
comment:55
Opened #31166 for the numpy fix |
This comment has been minimized.
This comment has been minimized.
comment:57
I was just curious if anyone was planning to open a ticket for scipy. I don't know enough about the sage build system, but it's possible to check if the user is on Big Sur by doing sw_vers | grep 11 and then based off of the result you could set MACOSX_DEPLOYMENT_TARGET=11.0 |
comment:58
During the Sage build process, Sage already defines an environment variable
This should be '20' for Big Sur. I'll open a |
This comment has been minimized.
This comment has been minimized.
comment:60
Replying to @jhpalmieri:
Actually, this is not correct: this variable is not universally defined anymore, so Sage packages that try to use it end up printing warnings. For example,
See #31186. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:63
Fails on a the as-vanilla-as-possible buildbot machine while building scipy (I take it thats #31326):
|
comment:64
You know the drill... full config.log, full log please |
comment:65
|
comment:66
For what it's worth, I am due for an upgrade and a test run of a Time Machine copy of my current (old) Mac onto a new Big Sur machine on an M1 chip apparently works - I'm not sure how, presumably using Rosetta somehow. Do we have any other data points about upgrading the Mac but leaving a working Sage install in place? (I guess upgrading that install would fall squarely under this ticket, though.) |
comment:68
I think we can close the ticket now - this task is done |
comment:69
Yes, I agree. |
This is to support macOS 11 Big Sur.
MACOSX_DEPLOYMENT_TARGET
problems - https://groups.google.com/g/sage-devel/c/Sj3YBVJoHQM/m/Zt-Ih_hJAwAJhomebrew-macos-11.0-xcode-minimal
:scipy
build failsRelated:
References:
Depends on #30494
CC: @dimpase @jhpalmieri @mkoeppe @slel @vbraun @williamstein
Component: porting
Keywords: macOS
Issue created by migration from https://trac.sagemath.org/ticket/30651
The text was updated successfully, but these errors were encountered: