https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80836
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- I'm unsure what exactly this report is about. The first half seems to be about building GCC itself, and ensuring it can find the libs that GCC relies on, right? That's simple, just build the support libs in-tree so there are no runtime dependencies on them. That's what the stackoverflow answer suggests, and is what happens if you follow https://stackoverflow.com/a/10662297/981959 which refers to https://gcc.gnu.org/wiki/InstallingGCC In short, stop installing libgmp.so, libmpfr.so and libmpc.so in non-standard locations and then trying to make GCC find them later. Just don't do that. Everything's much easier if you don't do that. The second half of this report seems to be about building your own programs using GCC, and ensuring they can find GCC's runtime libs. I agree that an option to add rpaths for GCC's own libs would be nice, but you can make it happen automatically by installing a custom specs file that adds -rpath to the *lib: spec.
