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

Build for ARM Macs? #493

Closed
spalger opened this issue Dec 1, 2021 · 9 comments · Fixed by #496
Closed

Build for ARM Macs? #493

spalger opened this issue Dec 1, 2021 · 9 comments · Fixed by #496

Comments

@spalger
Copy link

spalger commented Dec 1, 2021

I'm trying to develop on a Mac with a fully native toolchain and ibazel is the last tool which doesn't have an ARM build. I've tried running ibazel from brew using rosetta but it spawns a bazel server under rosetta too which causes other problems with the toolchain. I've also tried to build ibazel myself using bazel build //ibazel and get errors about no matching toolchains found for types @io_bazel_rules_go//go:toolchain...

Is there a chance that someone with more experience could at least put up a build of v0.15.10 for darwin-arm64?

@mistic
Copy link
Contributor

mistic commented Dec 3, 2021

Both me and @mrmeku did some experiments around this and ultimately trace the problem to fsnotify/fsevents#50

Last time we discussed this I was told @gregmagolan knows how to tackle it

@zoidyzoidzoid
Copy link
Contributor

Seems like a duplicate of #482 ?

Though this issue has more info about how to fix it.

@zoidyzoidzoid
Copy link
Contributor

Anyway anyone else can help with this problem, @gregmagolan?

I managed to run bazel build //ibazel on my M1 Mac, after updating rules_go, but I'm not sure if there is something else I need to run too.

@zoidyzoidzoid
Copy link
Contributor

I also tried to have a look at fsnotify/fsevents#50 , but I think for that we might need to do the different types of builds on machines with different architectures?

@zoidyzoidzoid
Copy link
Contributor

Sounds like @mistic figured it out in fsnotify/fsevents#50 (comment)

And hopefully #496 will fix it

Thanks @mistic!

@mistic
Copy link
Contributor

mistic commented Feb 3, 2022

Now we just need to get the PR I've opened to be able to move forward @zoidbergwill but it is still waiting for reviews

@achew22
Copy link
Member

achew22 commented Feb 4, 2022

Unfortunately all the PRs that claim to fix this do not pass CI. There is no path forward if CI is red, and I don't have an arm mac to do any testing on.

@mistic
Copy link
Contributor

mistic commented Feb 4, 2022

@achew22 I dont think that is true, the red CI is being caused by the miss of a28f528 which I've reverted as I was not sure about it and was waiting on your review to understand wether or not it make sense. I have arm hardware and I'm available to work with you to move the PR forward as long as you are available to do it...I will re-add the change and the CI will turn green.

@mistic
Copy link
Contributor

mistic commented Feb 4, 2022

Just reverted the change I mentioned and the CI is now green.

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 a pull request may close this issue.

4 participants