-
Notifications
You must be signed in to change notification settings - Fork 47
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
Unable to build/install on macOS Big Sur 11.0.1 #235
Comments
I've build things against Kerberos libs before but I'm not sure how the whole Frameworks-thing and building C-code for Python works, that's new for me. |
Can you provide the output of I'm not sure what's changed for the new macOS - perhaps @jborean93 knows? |
I'm updating my Macbook today to Big Sur so I can test it out. We are seeing that in our CI tests when trying to upgrade our macOS instances to Big Sur so hopefully it's a simple solution. |
Ok brace yourselves because this is going to be a bumpy ride 👍 The error from setup.py stems from this exception that occurs when In the case of Big Sur I found that
The root of this issue stems from a new feature (Under Kernel) on Big Sur
This means that the actual library file at $ ls -al /System/Library/Frameworks/GSS.framework/
total 0
drwxr-xr-x 5 root wheel 160 Jan 1 2020 .
drwxr-xr-x 202 root wheel 6464 Jan 1 2020 ..
drwxr-xr-x 3 root wheel 96 Jan 1 2020 Helpers
lrwxr-xr-x 1 root wheel 26 Jan 1 2020 Resources -> Versions/Current/Resources
drwxr-xr-x 4 root wheel 128 Jan 1 2020 Versions This is an issue because on all current releases of Python (3.9.1, 3.8.7, 3.7.9, 3.6.12) the The builtin version of Python provided by Apple has been patched so the
I prefer the 2nd option myself because it will only use the fallback if the framework could be found and if our hardcoded path doesn't work then Line 200 in 5ee095e
I'll probably open a PR with this change sometime soon. |
Here is my proposed fix #236. |
That's how far I got in the rabbit hole until I gave up = )
Except that it doesn't. Or at least some other problem arises:
Doesn't work with Homebrew Python either:
Works with Python installed via asdf though:
|
I don't feel bad anymore that I couldn't solve it ; ) Great work @jborean93 ! |
@jborean93 You win the Internet. |
Thanks @jborean93! While python/cpython#22855 is going to be backported some, current feeling seems to be that it won't land in 3.6/3.7. So we'll need to merge your workaround and maybe we can remove it again in a few years. |
@simmel that errror is because you don’t have cython installed and it’s expecting the .c files to already exist. Cython must be there at build time to generate the .c files. Normally they aren’t needed with the normal sdist but installing them from source does. |
Right! Thank you!
…On Thu, 2020-12-10 at 10:41:13 -0800, Jordan Borean wrote:
> Except that it doesn't. Or at least some other problem arises:
@simmel that errror is because you don’t have cython installed and it’s expecting the .c files to already exist. Cython must be there at build time to generate the .c files. Normally they aren’t needed with the normal sdist but installing them from source does.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#235 (comment)
|
Sorry to comment on this closed issue, but I noticed below msg , is it expected?
|
What went wrong?
Not possible to install
pip3 install gssapi
nor build via./setup.py build
on macOS Big Sur 11.0.1:How do we reproduce?
Build on Big Sur?
Component versions (python-gssapi, Kerberos, OS / distro, etc.)
The text was updated successfully, but these errors were encountered: