You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My hunch is that this might be a cargo bug, but I hope you all don't mind if I start here 😸
Basically, my main workstation is aarch64 and I'm trying to cross compile for amd64, but the following error occurs. Best I can tell it's because the GCC suite on aarch64 doesn't bother with -m64 since all binaries are emitted as 64-bit
We should be able to reproduce this if we use rust-cpp-hello-world cross-compiled from an ARMv8, but I simply don't have access to the hardware right now so I'll see if I can get a cloud instance to test this (somewhat difficult since Github Workflows and DigitalOcean don't seem to support ARMv8 machines).
This may be fixed when we have support for other toolchains in images #817, which would allow #751 to work, so the cross-compiler can run from an aarch64unknown-linux-gnu image and cross-compile to a x86_64-unknown-linux-gnu target.
alright! So, this issue is strange, as it's using the stable-aarch64-unknown-linux-gnu toolchain and not stable-x86_64-unknown-linux-gnu as it should have with #244, I suspect an old cross version was used (pre 0.1.15)
this does not replicate anymore, unless the wrong toolchain is used.
My hunch is that this might be a cargo bug, but I hope you all don't mind if I start here 😸
Basically, my main workstation is aarch64 and I'm trying to cross compile for amd64, but the following error occurs. Best I can tell it's because the GCC suite on aarch64 doesn't bother with
-m64
since all binaries are emitted as 64-bitThe text was updated successfully, but these errors were encountered: