public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/17311] Wrong libgcc_s.so.1 is used by lt-gij
Date: Mon, 06 Feb 2006 19:03:00 -0000 [thread overview]
Message-ID: <20060206190309.30587.qmail@sourceware.org> (raw)
In-Reply-To: <bug-17311-682@http.gcc.gnu.org/bugzilla/>
------- Comment #16 from hjl at lucon dot org 2006-02-06 19:03 -------
Please read the summary line: "Wrong libgcc_s.so.1 is used by lt-gij". Ld.so
will
search DT_RPATH first for any shared libraries. If you have DT_RPATH entries
pointing to installed paths to libraries/executables in the build tree, when
you
run such an executable in the build tree, the shared libraries in installed
paths
will be used, if they exist. That is the newly built shared libraries in the
build tree may never be used. Sometimes it is fatal if the shared library in
the
installed path isn't 100% compatible with the newly built one.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17311
next prev parent reply other threads:[~2006-02-06 19:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17311-682@http.gcc.gnu.org/bugzilla/>
2006-02-06 18:24 ` Ralf dot Wildenhues at gmx dot de
2006-02-06 19:03 ` hjl at lucon dot org [this message]
2006-02-07 5:48 ` Ralf dot Wildenhues at gmx dot de
2006-02-07 16:16 ` hjl at lucon dot org
2006-02-07 16:28 ` Ralf dot Wildenhues at gmx dot de
2006-02-07 16:48 ` hjl at lucon dot org
2006-02-07 17:18 ` Ralf dot Wildenhues at gmx dot de
2006-02-07 17:25 ` hjl at lucon dot org
2006-02-07 17:43 ` Ralf dot Wildenhues at gmx dot de
2006-02-07 18:45 ` hjl at lucon dot org
2006-03-01 17:39 ` hjl at gcc dot gnu dot org
2006-03-01 17:42 ` hjl at lucon dot org
2006-03-02 7:09 ` Ralf dot Wildenhues at gmx dot de
2004-09-03 20:27 [Bug libgcj/17311] New: " hjl at lucon dot org
2004-09-03 20:46 ` [Bug libgcj/17311] " mckinlay at redhat dot com
2004-09-03 20:52 ` hjl at lucon dot org
2004-09-09 3:42 ` pinskia at gcc dot gnu dot org
2004-09-09 16:25 ` hjl at lucon dot org
2004-09-14 18:42 ` hjl at lucon dot org
2004-09-16 0:11 ` hjl at lucon dot org
2004-10-11 20:13 ` tromey at gcc dot gnu dot org
2004-10-11 20:32 ` hjl at lucon dot org
2004-10-11 20:49 ` tromey at gcc dot gnu dot org
2004-10-11 21:01 ` hjl at lucon dot org
2004-10-11 21:27 ` tromey at gcc dot gnu dot org
2004-10-12 19:52 ` hjl at lucon dot org
2005-08-17 3:12 ` pinskia at gcc dot gnu dot org
2005-08-17 18:06 ` hjl at lucon dot 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=20060206190309.30587.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).