Skip to content
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

Add support for M1 Macs (missing darwin/arm build config) #1963

Open
the80srobot opened this issue Mar 17, 2022 · 5 comments
Open

Add support for M1 Macs (missing darwin/arm build config) #1963

the80srobot opened this issue Mar 17, 2022 · 5 comments

Comments

@the80srobot
Copy link

The Heroku CLI currently fails to install on M1 Macs, because the requisite tarball doesn't exist.

install.sh can figure out that it needs to set OS to "darwin" and ARCH to "arm", but fails because that tarball doesn't exist on cli-assets.heroku.com.

Can you please update your build config to produce a darwin/arm build?

@the80srobot
Copy link
Author

This is related to issue #1731 - I also commented there. The install.sh script might nee updating as well, but the core issue is that you're not producing arm builds for Mac.

@lukasmalkmus
Copy link

I just struggled with this as well (two years into ARM Macs and the homebrew formula is still broken for M1/M2 Macs? Come on...). Anyways, the tarball is now there but with the arch being arm64 instead of arm. I managed to install it by putting another elif statement in the script that checks for arm64 and sets the $ARCH=arm64 accordingly. That downloads and installs the correct tarball.

@k80bowman
Copy link
Contributor

@the80srobot I apologize for the delay in looking into this. We do produce https://cli-assets.heroku.com/channels/stable/heroku-darwin-arm64.tar.gz as shown in our documentation. Will that tarball work for you?

@davegaeddert
Copy link
Contributor

I had the same issue, and did the same thing. The tarball works fine but the install script just doesn't support it... #3013 is a potential fix!

@k80bowman
Copy link
Contributor

@davegaeddert the fix you gave us (thank you) has been released in the CLI, is it working for you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants