Closed issue by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/36379

Description:
Package `gcc-10.2.1pre1_3` ships binaries like `/usr/bin/x86_64-unknown-linux-gnu-gcc`, etc. However, `ccache-4.5.1_2` doesn't ship symlinks for these binaries.

One way this issue shows up is:
 -  In python3 sysconfig has `CC='x86_64-unknown-linux-gnu-gcc -pthread'`
 -  Building python extension modules (using setuptools) picks CC from sysconfig
 -  since ccache doesn't include a symlink for `x86_64-unknown-linux-gnu-gcc` the ccache is bypassed, in spite `/usr/lib/ccache/bin/` being in PATH.

A possible workaround would be to add symlinks for `x86_64-unknown-linux-gnu-gcc` etc in ccache.

NOTE: the cache entries are tagged by the compiler filename, so `gcc` and `x86_64-unknown-linux-gnu-gcc` would NOT share the cache (even if the compilers are the same, as in hardlinks of each other). I think this should not be a problem, since the same build system would use the same binary name.

Another (minor) issue is that `ccache` ships symlinks for `*-cc` compilers, but the gcc packages don't ship those (except for `/usr/bin/cc` which is a symlink to `/usr/bin/gcc`).

The same issue may happen for `x86_64-linux-musl-gcc`, etc. which are also not included in ccache.

CC: @Gottox