Problematic linking between glibc and shared libgcc

[Joe Buck]

> It's been a long-standing GCC policy not to use -rpath (or equivalent)
> when linking with any shared library so that people can move the
> libraries around later.
> 
> The argument for -rpath are that it makes things easier for users if
> you *don't* move stuff; the argument it against is that it makes
> things harder if you do.

What if there were a simple flag (which would not be the default)
saying to wire in the paths to the gcc-supplied libraries?  (Use of
this flag would be an error on platforms that don't support the rpath
concept).  Documentation for the flag would warn that binaries produced
this way won't run on machines that don't put the libraries in the
exact same places.