`./x check library/std --target=aarch64-kmc-solid_asp3` spuriously requires binaries to be in `PATH` about rust HOT 7 CLOSED

I just remember we have BOOTSTRAP_SKIP_TARGET_SANITY for this. You could simply execute BOOTSTRAP_SKIP_TARGET_SANITY=1 x check library/std --target=aarch64-kmc-solid_asp3 which should work just fine.

I need to list/document all these configurations somewhere..

from rust.

Ah thanks. I did not know about BOOTSTRAP_SKIP_TARGET_SANITY. This does allow me to check all the libstd targets.

from rust.

This check is done for all targets:

from rust.

Hm, well i did a bunch of checks on "weird" (aka tier 3?) targets and this was the only one that was a blocker for me. x86_64-unknown-hermit, wasm32-unknown-unknown, x86_64-fortanix-unknown-sgx, etc all worked fine.

EDIT to say that I'm interested in testing libstd and not so much in no_std targets.

from rust.

Wasm32 is explicitly excluded from this requirement a couple lines above the linked code. For the rest of the targets it may be that they use gcc rather than target-triple-gcc as C compiler by default, thus seemingly working, but producing object files for the wrong OS. The solid target spec explicitly specifies aarch64-kmc-elf-gcc as linker.

from rust.

But in this case they definitely aren't used. An empty file with the executable bit set definitely isn't producing any output.

from rust.

This can be worked around by creating empty files, marking them as executable and putting them in PATH because they're never actually called.

This seems to be more of a workaround than a proper solution (not really sure of there are any). And makes bootstrap more complicated to avoid it's own rules.

Perhaps we could make some adjustments to the target sanity check, but then there might be complications as mentioned by bjorn3:

Note that on many targets it actually is needed even for check mode as build scripts will still compile some C code even in check mode.

from rust.