-
Notifications
You must be signed in to change notification settings - Fork 10
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
milo/support aarch64 unknown gnu #123
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the linter error:
Could you be hitting ziglang/zig#4911 ? |
I think so. |
getting a new error this time. cc @NobodyXu - any ideas? |
right - now im trying to make it use the NDK version of ld. currently, when i move ld to /usr/bin, the shell doesn't pick up that there is something in that directory called |
cc @alsuren - any ideas |
c0e47d8
to
70c09fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please give your squashed commit a better name, and consider my suggestions (it may be that you already tried them)
I would quite like to try one of these binaries in docker on my m1 mac. Let's ship it and get it building stuff :D
i can't merge it because there are some review changes that haven't been addressed (even though they have). @alsuren could you merge it for me? thanks |
The "request changes" review is blocking the merge. I tend to avoid using that button because it feels impolite (I always tend to leave feedback as "comment"). I hadn't realised that it also blocks merging in the presence of other approvers :-(. If you want to smoke test it before we merge to main, push it to the |
alright, i'll push it! fingers crossed |
seems to have worked! should i delete the |
nvm, it's failing because it's using a weird version of the branch causing it to not have access to a file. in practice, this won't happen if this is merged and the cron just runs. ps @alsuren - can you not override the requested changes thing and merge it? |
Oh hey: there is a "dismiss review" item in the menu. I still think that https://github.com/cargo-bins/cargo-quickinstall/actions/runs/4033938309/jobs/6934774496#step:4:89 (
) is a problem that we're also going to see on main. Let me have a quick dig about. |
I just tested it out in arm docker, and Glancing at https://github.com/cargo-bins/cargo-quickinstall/pull/123/commits still doesn't tell me anything about what this PR is about, so it's likely to cause problems for anyone doing archaeology later (although they will have enough problems unpicking my commits, so they might not notice yours). Otherwise, you have an approval and I think you have merge access, so ship it. Now it's well past my bedtime. I might do some more quickinstall hacking tomorrow though. |
Woo! I'll squash my commits again. Just testing the actions branch then I'll give it a merge! |
…ickinstall to build binaries for the aarch64-unknown-linux-gnu target, using Zig as a linker for cross-compilation.
2e2647d
to
2e13042
Compare
Seeing some errors @alsuren 😬 https://github.com/cargo-bins/cargo-quickinstall/actions/runs/4034450545/jobs/6935671373#step:5:101 PS: I ran |
This error is caused by my PR #140, will fix it |
This allows
cargo-quickbuild
to build foraarch64-unknown-linux-gnu
.