public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/46607] [4.6 Regression] libgfortran relocated install fails
Date: Fri, 28 Jan 2011 09:11:00 -0000 [thread overview]
Message-ID: <bug-46607-4-Md7lrr2iUB@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 #11 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2011-01-28 07:38:06 UTC ---
Yeah, relinking, not prelinking, sorry.
I guess something along the lines of make_relative_prefix might work, if a
twisted maze of soft links doesn't make it unworkable. IIRC that's why libtool
decided to support DESTDIR but not arbitrary prefix changes.
In order to avoid relinking, you can configure with --enable-fast-install, but
I haven't checked this will work around the install-time complaint, and I'm
concerned that, at least on some systems, it might cause old preinstalled
dependency libraries to be used instead of just-built ones, in spite of GCC's
setting of SHLIB_PATH or equivalent. I guess it may be worth a shot if you
want to operate outside libtool's (current) specs.
All that said, this is probably not the right forum to discuss bugs or suggest
improvements for libtool. Heck, I haven't even been involved with libtool for
years, so I might as well back away slowly ;-) IMHO, odds are better of having
it resolved for good (improved or rejected) if you take it upstream. Now, if
you'd like to reopen this once it's in libtool's bug database, with a pointer
to it in “See Also”, just so that it's tracked in GCC's bug database, no
objections from me.
prev parent reply other threads:[~2011-01-28 7:38 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
2011-01-28 9:11 ` aoliva at gcc dot gnu.org [this message]
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-Md7lrr2iUB@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).