public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/46607] [4.6 Regression] libgfortran relocated install fails
Date: Thu, 27 Jan 2011 18:06:00 -0000 [thread overview]
Message-ID: <bug-46607-4-ZPnPZefLUk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46607-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46607
--- Comment #10 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-01-27 17:47:12 UTC ---
On Thu, 27 Jan 2011, aoliva at gcc dot gnu.org wrote:
> This could bring an improvement for a few platforms, but it wouldn't solve the
> problme in general. On platforms that don't support overriding e.g. DT_RPATH
> with e.g. LD_LIBRARY_PATH, the right thing to do is still to require
> prelinking. Libtool, in an effort to offer a standard interface, has decided
> to impose the requirement that the install-time libdir must end with the libdir
> specified at build time. This is not a bug, it's a correct design decision.
I don't see how prelinking (relinking?) relates to the relation between
two libdir values. What platform's shared library peculiarities allow
installation where one libdir is a prefix of the other but not more
general relations like those allowed by make_relative_prefix? As far as I
can see, it should be a straightforward generalization of any logic
supporting adding a prefix to libdir to support also removing some initial
directory segments first.
In fact, if you're relinking I don't see the need to care about the
configure-time directories at all. At build time, link only for the
build-tree paths, if any paths need hardcoding anywhere at all; at install
time, link only for the paths determined by the makefile variables at
install time; at both times, disregard the paths passed to configure
except insofar as they determine the makefile variables at install time.
Support for removing initial segments when installing would probably be
more of a straightforward change, however, but in any case it seems to be
a libtool bug to me.
next prev parent reply other threads:[~2011-01-27 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 18:20 [Bug libfortran/46607] New: " jsm28 at gcc dot gnu.org
2010-11-23 10:01 ` [Bug libfortran/46607] " rguenth at gcc dot gnu.org
2010-12-07 11:09 ` jakub at gcc dot gnu.org
2010-12-07 13:25 ` joseph at codesourcery dot com
2010-12-13 16:57 ` rwild at gcc dot gnu.org
2010-12-13 18:40 ` joseph at codesourcery dot com
2011-01-20 22:07 ` aoliva at gcc dot gnu.org
2011-01-24 23:45 ` joseph at codesourcery dot com
2011-01-25 9:03 ` rwild at gcc dot gnu.org
2011-01-25 17:01 ` joseph at codesourcery dot com
2011-01-27 4:26 ` aoliva at gcc dot gnu.org
2011-01-27 18:06 ` joseph at codesourcery dot com [this message]
2011-01-28 9:11 ` aoliva at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-46607-4-ZPnPZefLUk@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).