-
Notifications
You must be signed in to change notification settings - Fork 238
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
build or install on Apple M1 #579
Comments
@llaenowyd What does |
That's clarifying - if it's intended to be run with elevated privilege, I didn't realize.
and
|
@llaenowyd My bad - Unfortunately, I don't know for sure why the brew step is failing -- I don't currently have a mac to test it with. |
Oh I did not know that, ok. I'm discovering that homebrew introduces more variables with arm64 support - somewhat averse to using it until there's an "all good for m1" announcement, and as of now, nothing is installed with it:
|
Encountered this same problem on MacBook with M1 chip.
The reason why Follow the suggestion in error message and use
After tracing the source code, I think the problem is that Homebrew Formula use circleci-cli/.circleci/pack.sh Lines 15 to 32 in 605a617
The values of
This make the value of |
Hello, Homebrew maintainer here. When Homebrew/homebrew-core#79094 is merged, CircleCI CLI will be bottled (available via binary package) on ARM. We prefer using Homebrew formulae over vendored dependencies and in this case, that seemed to be the solution to getting CircleCI CLI built on M1. I had some issues getting Thanks! |
hello @llaenowyd , did you have any luck recently on this? 🤓 I just wanted to mention that I am now able to install the CircleCI CLI via homebrew on Apple M1 successfully.
|
Closing as there's no answer from OP |
Meta:
CircleCI CLI Version:
latest
Operating System:
BigSur
CircleCI CLI Diagnostic:
Following brew instructions:
Following alternative installation method:
but
and
Looks like a scripting problem in both cases TBH, possibly not directly due to the cpu arch?
The text was updated successfully, but these errors were encountered: