-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
macOS: spkg-install scripts that force use of clang conflict with '-march=native' #30725
Comments
This comment has been minimized.
This comment has been minimized.
Dependencies: #31186 |
Changed dependencies from #31186 to none |
This comment has been minimized.
This comment has been minimized.
comment:8
Those bits should have gone when I "normalised" clang for building sage on OS X. We were probably planing to remove them at a later stage and forgot. Well, the opportunity is clearly now. New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:10
Also several of these packages have been updated since and are able to build with an actual gcc on macOS. We have tickets for some packages where this is still broken: #29613 (givaro) |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Author: Matthias Koeppe |
comment:15
I have tested the configuration in the ticket description successfully. But testing with the
|
comment:16
Btw, to prevent breackage because of |
comment:17
Yes, if simple fixes such as package upgrades don't fix it, that's what we should do. |
comment:18
Upgrade of cmake to 3.19.3 (#31258) does not fix this |
comment:19
I don't understand - I presume one still cannot build all of Sage on macOS using "real" gcc. Why is this a blocker? |
comment:20
Replying to @dimpase:
Yes, this is what the experiment with
When Apple's compiler is invoked as |
This comment has been minimized.
This comment has been minimized.
comment:35
R does not use Anyway, I think the main problem is that we run New commits:
|
comment:37
Replying to @kliem:
... is it ignoring CFLAGS? |
comment:38
No, it already uses
|
comment:39
Ah, OK, thanks |
comment:40
R was one of the things that crashed or didn't build with |
comment:41
My tests finished. Not very sucessfull though. Looks like zlib failed for many mac runs. Also ubuntu-bionic-minimal and debian-buster-minimal failed because somehow ssl wasn't available and the pytest failed (or the server did not reply). Anyway. There are several different ways to fix |
comment:42
Replying to @kliem:
One needs to merge a few tickets that fix up the GH Actions runs. |
comment:43
Replying to @kliem:
Are you satisfied with the version that you pushed? |
Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/496953211, https://github.com/mkoeppe/sage/actions/runs/496953208, Jonathan Kliem, https://github.com/kliem/sage/actions/runs/498284561 to https://github.com/mkoeppe/sage/actions/runs/502363182, Jonathan Kliem |
comment:46
And I'm also happy with your changes. I'm just waiting on an okay, that this fixes things. |
comment:47
Is this supposed to fix issues around using /usr/bin/python3 on Big Sur? With this ticket if I configure with-python=/usr/bin/python3 and then do make Cython I still get
|
comment:48
Does it go away, if you additionally pull in #31228? This one just disables |
comment:49
Replying to @zlscherr:
No, it's only a first step |
comment:50
Replying to @kliem:
Thanks! Yes, with this ticket and #31228 I can get python packages (at least cython) to build again using system python. I'll continue to check to make sure everything builds. |
comment:51
I think this is good to go. |
Changed reviewer from https://github.com/mkoeppe/sage/actions/runs/502363182, Jonathan Kliem to Jonathan Kliem |
Changed author from Matthias Koeppe to Matthias Koeppe, Jonathan Kliem |
Changed reviewer from Jonathan Kliem to Jonathan Kliem, Matthias Koeppe |
Several packages force the use of
clang
because they cannot be built with a real gcc due to the use of Apple language extensions in system header files.For these packages, the use of
-march=native
introduced in #27122 causes build errors becauseclang
does not understand these flags (even though/usr/bin/gcc
does).Tickets where code setting the compiler was explicitly introduced: #22999 (cmake), ....
To test:
To test with a real gcc (using a gcc-10 installed from homebrew):
CC: @jhpalmieri @dimpase @kliem @zlscherr @kiwifb @seblabbe
Component: porting
Author: Matthias Koeppe, Jonathan Kliem
Branch/Commit:
f56e65e
Reviewer: Jonathan Kliem, Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/30725
The text was updated successfully, but these errors were encountered: