-
Notifications
You must be signed in to change notification settings - Fork 13
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
Can't build crash-context on arm-unknown-linux-gnueabihf #5
Comments
These are working fine: https://github.com/msirringhaus/minidump_writer_linux/actions/runs/1992598643 |
Hmm, I will install cross locally and try and figure out what the actual error is, as you say the error output from GHA is useless. |
I get the same unhelpful error message locally, too. |
I can't even get cross working locally at all because I use podman and using main switched to GHCR which doesn't have proper image tags. 😛 |
Ahh nvm [target.arm-unknown-linux-gnueabihf]
image = "ghcr.io/cross-rs/arm-unknown-linux-gnueabihf@sha256:2c7f685d79baa15a6437c9ccb76381ad2f597eec62e1a27f9c11fea5ce2adbf6" |
I suspected it was the |
I've bumped and published crash-context to 0.0.2. |
Just to confirm: This seems to indeed fix it: https://github.com/msirringhaus/minidump_writer_linux/actions/runs/1993088807 |
@Jake-Shadle @msirringhaus
|
Can you please add what target triple doesn't compile and what the compile error actually is? |
Here is the mysterious error message: error: :23:1: invalid instruction, any one of the following would fix this: error: could not compile |
Ok well I'm not seeing that, either you are using a different target triple or you're on an older version of rustc? |
The error only occurs when using the 'release' flag. Building without the flag is successful. |
I'm unable to build crash-context on arm-unknown-linux-gnueabihf, either locally (using a raspberry pi) or using github actions: https://github.com/msirringhaus/minidump_writer_linux/actions/runs/1992494641
Unfortunately, the error is only
even when running
--verbose
.Is this supposed to work?
The text was updated successfully, but these errors were encountered: