Alexander Huszagh

Waiting on #1006 to merge, since this will be handy for native/non-native Dockerfiles for CentOS.

Currently adding the concept of a native CentOS image and then have a specialized x86_64 one since we now support an aarch64 CentOS image. I'll be factoring in the requested...

Other things: `TargetTriple::DEFAULT` should support more than just `X86_64UnknownLinuxGnu`. This should likely be the default Docker platform, if we provide images for it, or `X86_64UnknownLinuxGnu`, if possible.

> How does one build the native image for other platforms? Just using `cargo build-docker-image aarch64-unknown-linux-gnu` if using an ARMv8 Linux or mac M1 Docker host, or by doing `cargo...

@simao, that's a very different error than the first one, which seems to be memory exhaustion. Yours seems to be an issue with cross-compilation and proc macros, which I believe...

# Proc Macros Pretty sure this is an issue where proc macros are built for the host rather than the target. If I try to compile a simple crate that...

I believe this is an issue with proc macros compiling for the host, and any dependencies or crates using the proc macro compile for the target, and is a more...

This no longer reproduces as of the latest main, using this sample [project](https://github.com/Alexhuszagh/issue_605). ```bash $ cross build --target aarch64-unknown-linux-gnu .... Compiling futures-intrusive v0.4.0 [50/923] Compiling tokio-stream v0.1.9 Compiling digest v0.10.3...

Can you post reproducing sample code? Is your project open source? Re-opening this because it only seems the fix was partial.

That's going to make it difficult to debug without a reproducing example, so fixing this might take a while. If anyone has a minimum, reproducing example or open-source code that...