-
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
Feature/Discus request regarding canadian-cross compiling the toolchain #27
Comments
I'm a bit confused here. So you're trying to build on |
The host which is building the binary is x86_64 So in the end we would have a musl gcc compiler which runs on aarch64 and compiles to armv6 but all was build first on a x86_64. |
Thanks for clarifying. The script doesn't currently self-host, but what you could probably do is
In step 3, you'll need to run |
I have enabled discussions for this repo, feel free to use it. |
Hello there,
Because discussions is not enabled for this repo, I place it here, as it's not an issue.
I wonder if someone every tried to do a canadian-cross compile with this?
What my main goal is.
x86_64-linux-gnu
systemarmv6-linux-musleabihf
for exampleaarch64-linux-gnu
This way it would be possible to build cross-compilers for all the provided targets but then are able to run on a arm64/aarch64 host/architecture.
Else something like QEMU needs to be used to emulate the aarch64 architecture, which is probably not going to provide the best performance.
Someone an idea, or tried this before either using mussel or something else? And if so, does someone have any pointers?
Thanks in advance!
btw. I already tried to install the
aarch64-linux-gnu-g**
cross compilers, use that as GCC/G++ and added the correct--host
and--build
arguments to the configure commands.The text was updated successfully, but these errors were encountered: