-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Python can build with GCC on macOS now #43430
Comments
Sigh. Well, maybe not. I just tried this on another machine (M1 not M2, but should be the same) and:
I know that curses as a prereq built:
so I'm a bit out of my league. @skosukhin and @scheibelp do you have any thoughts. I mean...it did work once... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In trying to see if my ye olde issue is still happening (see #34953), I decided to try on my newer laptop to force everything to be gcc 13 and then figure out what might be the cause of the oddity.
So, the only compiler in
compilers.yaml
? GCC 13. The only compiler inpackages.yaml
? GCC 13. But when I tried that I got:Hmm. So I went to that PR URL on python/cpython which is closed now but points to a new PR (python/cpython#20176) which is merged.
So I did the usual rash thing,
spack edit python
, commented out the conflict, and thenspack install python
and...it worked.I'm not sure of how to make a PR to add a
when
to the conflict a lalibuv
. I'm guessing there is some version of python where this started working. Does anyone know enough python development dates of release to help bracket it so I could do some test builds to see when things fail?The text was updated successfully, but these errors were encountered: