https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111605
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- This is only a problem when using a cross gcc, so why should mold proactively create symlinks for dozens of targets when mold is installed? It seems to me that a single symlink only needs to be created by the person building the cross-gcc, and installed alongside $target-gcc as part of that toolchain. This is not mold's problem, and could just be documented as part of gcc's installation docs. Although it probably does make sense for gcc to just fallback to using ld.mold without the target prefix.
