-
Notifications
You must be signed in to change notification settings - Fork 99
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
Be able to build from aarch64
#10
Comments
aarch64
Hi! Thanks for the report It may be possible to make the error message a bit clearer, yes. The compilation issue comes from the fact that the assembly code is using the GNU as syntax. If you are using You can try to use a different assembler by setting the path to it with the Rewriting all the assembly code under the Intel syntax would be relevant since the inline assembly in the Rust code is already written using the Intel syntax (for consistency). However I have to think about a way to make sure compilation is possible with both GNU as and nasm. |
By all means please do not feel obligated to waste precious cycles trying to figure out how to compile this from Apple Silicon Mac OS X (probably not a super common usecase), just thought I'd provide an example of why even with a bunch of |
Seems like there's an issue here: https://github.com/llenotre/maestro/blob/master/build_impl/compile.rs#L23-L24 Not sure if it's because I'm using
If i change
I have 0 clue where |
Kind of a confusing error because there is a
.cargo/config.toml
:but I'm guessing it expects something different
Doing this:
gets me further. not sure if this could be documented somewhere more clear
but then I get a whole bunch of weird
cc/clang
errors:It's probably because I'm on
aarch64
and it's trying to use$CC
without realizing it needs to "cross-compile" I guess?Not sure if the build.rs script or whatever can detect it needs to find x86/x86_64 compiler if one isn't available natively. I would have guessed changing the build target in
.cargo/config.toml
was enoughThe text was updated successfully, but these errors were encountered: