configure: Check CC_STAGE0 for --target support
We previously only checked the stage 1/2 compiler for --target support. We got away with this for quite a while but it eventually caught up with us in #21579, where `bytestring`'s new NEON implementation was unbuildable on Darwin due to Rosetta's seemingly random logic for determining which executable image to execute. This lead to a confusing failure to build `bytestring`'s cbits, when `clang` tried to compile NEON builtins while targetting x86-64. Fix this by checking CC_STAGE0 for --target support. Fixes #21579.
Name | Stage | Failure | ||
---|---|---|---|---|
failed
|
nightly-x86_64-linux-deb10-no_tntc-validate | Full Build | ||
|
||||
failed
|
pages | Deploy | ||
|
||||
failed
|
perf-nofib | Testing | ||
|
||||
failed
|
lint-submods | Tool Lint | ||
|
||||
failed
|
nightly-armv7-linux-deb10-validate | Full Build | ||
|
||||
failed
|
nightly-x86_64-freebsd-validate | Full Build | There has been a timeout failure or the job got stuck. Check your timeout limits or try again | |
|
||||
failed
|
nightly-x86_64-linux-deb10-validate+thread_sanitizer | Full Build | ||
|
||||
failed
|
nightly-x86_64-linux-alpine3_12-validate+fully_static | Full Build | ||
|
||||
failed
|
nightly-x86_64-linux-alpine3_12-int_native-validate+fully_static | Full Build | ||
|