On 5 July 2012 13:21, Vincent Lefevre wrote: > On 2012-07-05 15:07:53 +0300, Kai Ruottu wrote: >> The '--with-*' options only advice the compile time linker to find >> the right libraries but don't do anything for the runtime >> situation... > > Ah, OK. Why isn't this fixed, e.g. by adding --with-* paths to > the runpath of the generated executables needed for the build? The --with-xxx options only affect -I and -L GCC never adds runpaths to executables by default. This is also a FAQ: http://gcc.gnu.org/faq.html#rpath > I'd say that the goal of the --with-* options is to provide the > paths when they are not in the default environment (including > the runtime linker). What if the location of those libs during bootstrap is not the same as the location will be when the installed compiler is used? The docs at http://gcc.gnu.org/install/configure.html do tell you this might be necessary: "You might also need to ensure the shared libraries can be found by the dynamic linker when building and using GCC, for example by setting the runtime shared library path variable (LD_LIBRARY_PATH on GNU/Linux and Solaris systems)."
