Previously if no matching multilib was found then the user would
typically see an error like "fatal error: 'stdio.h' file not found"
which gives no indication as to the underlying problem.
With this change the user will instead see an error like
clang: error: no multilib found matching flags: --target=thumbv7em-none-unknown-eabi -march=... clang: note: available multilibs are: --target=armv4t-none-unknown-eabi --target=thumbv6m-none-unknown-eabi -mfpu=none ...
I'm not sure what the purpose of this addition is. It doesn't seem to be listed in the expected error messages (but it's presumably being printed anyway, and skipped over because the checks don't say -NEXT?). Did it sneak in here from another commit, perhaps?