public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu 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, 11 Oct 2004 20:49:00 -0000 [thread overview]
Message-ID: <20041011204938.20129.qmail@sourceware.org> (raw)
In-Reply-To: <20040903202714.17311.hjl@lucon.org>
------- Additional Comments From tromey at gcc dot gnu dot org 2004-10-11 20:49 -------
I read that. What I observe is that .libs/gij is created
by the build. Then if I run gij (not .libs/gij), it creates
.libs/lt-gij.
My understanding is that --enable-fast-install is what makes
all this work as it does. .libs/gij has the install tree
in its DT_RPATH -- but that is ok since this executable is never
run from the build tree. It exists only so that installation
can be as simple as "cp".
.libs/lt-gij is relinked lazily, when gij is run. Its DT_RPATH
is:
opsy. readelf -d .libs/lt-gij |grep RPATH
0x0000000f (RPATH) Library rpath:
[/home/tromey/gnu/Trunk/build/i686-pc-linux-gnu/libjava/.libs:/home/tromey/gnu/Trunk/install/lib]
So to me it looks like we're missing an entry here for the libgcc_s.so
directory. So, probably, your first patch is the way to go... I'd like
a bona fide libtool expert to look at this though.
I still don't understand why the second patch is needed.
As for --disable-fast-install, did you try just passing that to the
top-level configure? (I didn't)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17311
next prev parent reply other threads:[~2004-10-11 20:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[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
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
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=20041011204938.20129.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).