* The conda fv-main env activates BOTH gcc_linux-64 and gcc_linux-aarch64
triplets on every `conda activate` (alphabetical order makes aarch64
win), so on an x86_64 host the inherited `CC=aarch64-conda-linux-gnu-cc`
defeated the script's `: "${CC:=...}"` deferred default and tripped
x264's compiler probe with "unknown value 'native' for '-march'".
* Replace deferred defaults with unconditional assignment per
`uname -m`. Matches the team playbook's `export CC=...` semantics
verbatim.
* Print the toolchain banner up front so future probe failures are
diagnosable from the first lines of stdout.
Co-authored-by: Junda (David) Su <90978028+Davids048@users.noreply.github.com>
Co-authored-by: Matthew Noto <99706358+RandNMR73@users.noreply.github.com>
Co-authored-by: XOR-op <17672363+XOR-op@users.noreply.github.com>
Co-authored-by: Zhang Peiyuan <42993249+jzhang38@users.noreply.github.com>