This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/46607] [4.6 Regression] libgfortran relocated install fails
- From: "rwild at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 25 Jan 2011 06:40:35 +0000
- Subject: [Bug libfortran/46607] [4.6 Regression] libgfortran relocated install fails
- Auto-submitted: auto-generated
- References: <bug-46607-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46607
--- Comment #7 from Ralf Wildenhues <rwild at gcc dot gnu.org> 2011-01-25 06:40:20 UTC ---
(In reply to comment #6)
> I would note incidentally a suggestion (comment #3) to work around the
> general libtool bug on MinGW by stopping it relinking on MinGW. I don't
> believe there's any good reason for it to be relinking for GCC builds to
> ELF targets either, so perhaps stopping relinking there would help avoid
> this problem in many more cases.
But there is a good reason to relink on ELF: uninstalled libraries and
executables get DT_RPATH entries against uninstalled libraries they depend on,
so that uninstalled programs can be executed in a test suite before installing
the libraries they depend on. Removing (or replacing) those DT_RPATH entries
is the point of relinking. That GCC takes care of the uninstalled paths in
some other way as well is something libtool cannot know.