Fix cross compilation to xtensa-esp32s3-espidf

[NobodyXu]

Fixed #1552

[Vollbrecht]

@NobodyXu thanks for fixing that stuff. A bit of background i may add here. The espressif provided C toolchain did go through some naming schema changes. E.g starting with 13.2.0 they introduced a multilib for all xtensa targets. Previously it was needed to specifically call xtensa-esp32s3-elf xtensa-esp32s2-elf etc.

But since then this should not be needed anymore technically. They still provided wrappers for the "old" naming convention and ship them. They are actually "rust" wrapper to make it extra fun if you have a look here.

So with respect to the fix i am not so sure if hard-coding this in the long run is even the correct thing here. I think something with OP's setup was otherwise wonky, e.g explicitly hard coding this stuff now is not a proper fix.

Still thank you for your work on the cc crate. =)

If you run into problems with the xtensa / riscv espressif targets feel free to ping me or @ivmarkov in the future btw.

[NobodyXu]

That'd be great!

i can update https://github.com/rust-lang/cc-rs/blob/main/src/lib.rs#L3459 to have this prefix, and then fallback to the old name if the new name doesn't exist.

cc @Vollbrecht what if the new name of the compiler?

[sansmoraxz]

@NobodyXu isn't it better to put the toolchain name in fn prefix_for_target?

This approach would make growing the function too clunky. As there are other compiler targets.