https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111605
--- Comment #10 from Rui Ueyama <rui314 at gmail dot com> --- > 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's because there are too many and we don't have an exhaustive list of all possible triples. In particular, the vendor part of a triple (e.g. "none" in "arm-none-eabi") can be anything IIUC, so we can't make an exhaustive list of all triples. > 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. That's the correct solution if mold is bundled as part of the cross toolchain. But if a user of the cross gcc toolchain wanted to use the system-installed mold, they explicitly create a symbolic link in a $PATH by themselves at this moment. I think that's pretty inconvenient. > Although it probably does make sense for gcc to just fallback to using > ld.mold without the target prefix. Yeah, that's exactly what I want...
