If we’re cross-compiling for darwin on aarch64 hardware, we need to use a Clang that will run on that hardware.
Only tested in a Linux Docker container (aarch64-unknown-linux-gnu), running on an Apple M1 mac-mini (aarch64-apple-darwin20.5.0).
If we’re cross-compiling for darwin on aarch64 hardware, we need to use a Clang that will run on that hardware.
Only tested in a Linux Docker container (aarch64-unknown-linux-gnu), running on an Apple M1 mac-mini (aarch64-apple-darwin20.5.0).
If we're cross-compiling for darwin on aarch64 hardware, we need need to
use a Clang that will run on that hardware.
Only tested in a Linux Docker container (aarch64-unknown-linux-gnu),
running on an Apple M1 mac-mini (aarch64-apple-darwin20.5.0).
If we’re cross-compiling for darwin on aarch64 hardware, we need to use a Clang that will run on that hardware.
To be precise, you mean “run natively”, as x86 code could be run on aarch64 hardware via Rosetta layer, right?
To be precise, you mean “run natively”, as x86 code could be run on aarch64 hardware via Rosetta layer, right?
I’m talking about cross-compiling for Darwin, using Linux, on aarch64 hardware. I’m not sure what Rosetta is going to help with in that case.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
What guix HOSTS= do I use?
HOSTS="x86_64-apple-darwin18"