-
Notifications
You must be signed in to change notification settings - Fork 101
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
PyKerberos on MacOS - failure to install #189
Comments
Hi, could you share the original error without specifying |
Here is a build with the failure on PyKerberos:
Here is the install with the ARCHFLAGS set:
|
Again, I'm not sure if this is the best or right way to do this, but sharing as a workaround. |
We have also got another failure that I cannot personally reproduce but my colleague can consistently get to fail. His has to do with memcpy() and mempcpy() in glib vs stdlib I think. No idea why exactly he gets this error and I don't but guessing it has to do with our build environments being slightly different someplace.
I have no workaround for this one. |
The PyPI page for pykerberos does not provide a link to the official upstream source code: https://pypi.org/project/pykerberos/ (with a After verification, the source code for this PyPI package actually comes from https://github.com/02strich/pykerberos/ which has a v1.2.1 tag from 2017/12/20 too:
But that repository currently states:
Note the missing Which links us to https://github.com/apple/ccs-pykerberos that is actively maintained but has no v1.2.1 tag.
We probably should try and move to https://pypi.python.org/pypi/kerberos PS: Fun fact, all these are developed by Apple and/or derived from their work :) |
There's an open issue on requests-kerberos to switch from pykerberos to kerberos: requests/requests-kerberos#63 Given the last comment, it is probably easier trying to switch from requests-kerberos to requests-gssapi. Also:
See https://pypi.org/project/requests-gssapi/ |
@mcgarrah can you try installing |
Here is the logs for trying the install without ARCHFLAGS:
|
Here is the same run with ARCHFLAGS set...
|
Does the same happen with a python3 installed with HomeBrew ? Hint taken from: |
Maybe you need to update the system Python to 3.8.6+: giampaolo/psutil#1842 (comment) |
The Python 3.8.2 from brew fixed the requests-gssapi install using the /usr/local/bin/pip3 install method. So there is something going on with python versions along with pip. |
Something confuses me, I see Isn't macOS Big Sur v11.x the first official release to support those Apple silicon M1 chips? Or is it just your Xcode and macOS SDK that aren't up to date? |
Both my colleague and I are on Intel-based MacBook Pro 2019 machines. I assumed the arch issue was related to the non-Intel processor coming but we don't have them. That was why I mentioned the M1. |
Alright, that clears things up. Let's just add both workarounds to the README:
|
Another finding, building gssapi may not be needed on macOS 10.7.0+: https://github.com/pythongssapi/python-gssapi/blob/v1.7.0/setup.py#L62 |
There is an issue with pip installing PyKerberos on MacOS. The ARCH has to be set during the install or it fails. MacOS is no longer just "x86_64" and this is showing up in some libraries as the M1 processor is coming into play. I hacked around it for my installation with the following command after brew installing the base OS libraries.
% ARCHFLAGS="-arch x86_64" pip3 install aws-adfs --user
Just in case someone hits this I figured I throw it out there. It would be nice to have an option to not have krb used on Mac.
If someone has a better solution, please pile on.
The text was updated successfully, but these errors were encountered: