From: Mike Frysinger <vapier@gentoo.org>
To: binutils@sourceware.org
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Daniel Jacobowitz <drow@false.org>
Subject: Re: compile failure due to undefined symbol
Date: Tue, 02 Oct 2007 20:49:00 -0000 [thread overview]
Message-ID: <200710021352.35623.vapier@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710021614290.32726@blysk.ds.pg.gda.pl>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Tuesday 02 October 2007, Maciej W. Rozycki wrote:
> We have this RPATH_ENVVAR setting in the top-level directory. It breaks
> things. For my setup (Linux configurations) it adds some build
> directories to LD_LIBRARY_PATH. It breaks system-installed tools when
> building a cross-toolchain, because the newly-built BFD library, although
> for the same host, has a different target. But for a libtool-based setup
> there should be no need to use LD_LIBRARY_PATH or anything like this at
> all. This is because libtool has explicit support for running uninstalled
> newly-built binaries via the "--mode=execute" option. This option, under
> the bonnet, does all the relinking/rpath/whatever hassle is required for
> the given platform. All that is required is that .la files are used to
> refer to libraries dependent on during the build and libtool.
this is what we came to in a previous thread as well:
http://sourceware.org/ml/binutils/2007-07/msg00401.html
ive been simply deleting RPATH_ENVVAR in the toplevel configure for Gentoo ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2007-10-02 17:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 13:42 Peter S. Mazinger
2007-09-01 0:17 ` Alan Modra
2007-09-01 0:47 ` Peter S. Mazinger
2007-09-28 8:56 ` Nick Clifton
2007-09-28 12:23 ` Peter S. Mazinger
2007-09-28 12:55 ` Nick Clifton
2007-09-28 13:48 ` Peter S. Mazinger
2007-10-02 11:05 ` Nick Clifton
2007-10-02 13:13 ` Peter S. Mazinger
2007-10-03 11:06 ` Peter S. Mazinger
2007-10-04 14:13 ` Nick Clifton
2007-10-04 15:02 ` Peter S. Mazinger
2007-10-04 16:26 ` Nick Clifton
2007-10-04 21:01 ` Peter S. Mazinger
2007-10-05 9:02 ` Peter S. Mazinger
2007-10-08 10:45 ` Nick Clifton
2007-10-08 13:41 ` Peter S. Mazinger
2007-10-08 13:51 ` Peter S. Mazinger
2007-10-08 17:55 ` Nick Clifton
2007-10-02 14:23 ` Daniel Jacobowitz
2007-10-02 14:41 ` Nick Clifton
2007-10-02 15:01 ` Daniel Jacobowitz
2007-10-02 15:07 ` Nick Clifton
2007-10-02 15:07 ` Nick Clifton
2007-10-02 15:30 ` Daniel Jacobowitz
2007-10-02 15:35 ` Nick Clifton
2007-10-02 15:36 ` Daniel Jacobowitz
2007-10-02 15:51 ` Nick Clifton
2007-10-02 17:52 ` Maciej W. Rozycki
2007-10-02 15:13 ` Daniel Jacobowitz
2007-10-02 15:41 ` Maciej W. Rozycki
2007-10-02 20:49 ` Mike Frysinger [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=200710021352.35623.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=macro@linux-mips.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).