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 darwin arm64 builds #5523

Merged
merged 1 commit into from
Nov 12, 2023
Merged

Add darwin arm64 builds #5523

merged 1 commit into from
Nov 12, 2023

Conversation

dzbarsky
Copy link
Contributor

Github claims they have arm64 runners but doesn't seem like they enabled them for free plans. So for now, we cross-compile from intel and skip tests. I verified that some basic smoketests passed on my M1.

@sylvestre
Copy link
Contributor

@dzbarsky nice to see you here, small world :)

@cakebaker cakebaker merged commit cac9d5f into uutils:main Nov 12, 2023
50 of 52 checks passed
@cakebaker
Copy link
Contributor

Thanks for your PR!

@dzbarsky
Copy link
Contributor Author

@cakebaker Thanks for merging! I think we need a tagged release to trigger the builds, do you have one planned any time soon?

@cakebaker
Copy link
Contributor

@dzbarsky I don't know when the next release is planned as we don't have a fixed release schedule. Maybe @sylvestre can tell you more as he usually does the releases.

@sylvestre
Copy link
Contributor

sure
@dzbarsky is that urgent? thanks

@tertsdiepraam
Copy link
Member

@dzbarsky Isn't it running on main now? For example here: https:/uutils/coreutils/actions/runs/6841104107/job/18601127873

Or do you specifically want artifacts built for this target?

@DavidZbarsky-at
Copy link

Yes, I'd like to consume the released artifacts. It's not super urgent, but it is blocking increased usage of this project in bazel-contrib/bazel-lib#622, which is a pretty core part of the Bazel ecosystem at this point, since a lot of people use M1/M2 for local development. I'd love to get that in before they ship their 2.0, which is probably soonish but could wait for this fix.

I considered publishing my own binaries but it's less sketchy to have them come from the canonical upstream :)

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

Successfully merging this pull request may close these issues.

5 participants