-
Notifications
You must be signed in to change notification settings - Fork 58
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
Following installation instructions results in wget error on macOS #570
Comments
Just for additional info, I think this is a M1 specific error. I tested it on my machine and I had no problem. I have a non-M1 Mac |
Hey @colinvwood, has |
I have an M1 mac, and just tested - the Native Install Instructions for macOS (Apple Silicon) are working for me. |
Hey @lizgehret wget installed via conda has worked in the past but not for a while for me. That's interesting @gregcaporaso yeah I guess I figure we would have seen this on the forum if it were affecting more people. Once I had it happen on two different machines I thought it was worth an issue though. |
@colinvwood hmm that's interesting. I remember you had some issues with conda a while back when we were sorting through the conda vs mamba install - was it around that time? I'm wondering if you may want to just try installing wget via pip in your base env (since I don't think it particularly matters how wget is installed for qiime2 env stuff). I did find one anecdotal SO post where someone with an M1 mac mentioned having to go through some circuitous install steps for wget, but I couldn't find any additional information on that, so not sure how reliable that is. |
I installed |
Following the native installation instructions fails at the
wget <link to env file>
step with the following error:All previous steps succeed. This happens for me on two different M1 machines, one running Sonoma 14.1.2 and one running Ventura 13.2.1. Failures occur with a freshly installed Miniconda environment, as the docs suggest.
Updating the instructions to use
curl -L -O <link to env file>
instead ofwget <link to env file>
is a possible solution.The text was updated successfully, but these errors were encountered: