Installing gcc with `make install` on x86_64 Linux creates files "prefix/bin/c++" and "prefix/bin/g++" that are hard linked together. It is more convenient for me to make "prefix/bin/c++" a symbolic link to g++ instead. I have two questions: - Could doing this break any common processes that interact with g++, e.g. detection by CMake or Bazel? - Why does `make install` create hard links (a/o/t symbolic links) in the first place? Maybe not all platforms have symbolic links, but x86_64 Linux always does as far as I know. On many systems, there is a file "/usr/bin/cc" that is a symbolic link to gcc (or another C compiler), and this appears to work fine. It also seems bad to create hard links like that, so maybe the GCC build files could be updated to change this behavior. I could probably do it myself if it would be helpful. Or maybe there's a good reason for the hard link! Please let me know if this is the case.
