-
Notifications
You must be signed in to change notification settings - Fork 15
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
Failed to install via pip on M1 Mac #13
Comments
I am having the same issue on an M1 Mac. The only solution I have found so far is to install build nlpot as described in the and on Stackoverflow ( LINK ) (the post by hoefling helped me a lot). This works without problems but is a bit cumbersome. |
conda install nlopt also works How can we fix the pypi install for M1? |
I was successfull on Android ARM64 Termux Python3.9 |
I have an M1 mac and am wondering if there is any way I can help with this, as one of my python projects depends on nlopt and it has been a pain to compile myself and for others who want to collaborate. As far as I understand, you merely need someone with an M1 mac to generate the tarball or wheel file and then you can add that to pypi, right? |
+1 here. It's the same for M2. |
I see a similar error on mac with M3. |
I have the same issue and it would be great if we can solve this issue. |
Just in case if someone like does also not know about Install MambaYou can install it with brew install --cask mambaforge After the installation you need to run mamba init "$(basename "${SHELL}")" Create a Mamba EnvironmentInstead of using mamba create --prefix ./.mamba python=3.11 Python 3.11 is the latest version at the moment. Activate the conda environment with mamba activate ./.mamba Now you can install mamba install nlopt If you need a package which is not available in the conda repositories, you can still use |
Hi,
I was trying to install this on an M1 Macbook and got the following error
Is this an issue with the M1 mac or something else. Is it possible to help me take a look at this?
Thanks in advance!
The text was updated successfully, but these errors were encountered: