public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "Ralf dot Wildenhues at gmx dot de" <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: Tue, 07 Feb 2006 17:43:00 -0000 [thread overview]
Message-ID: <20060207174345.21229.qmail@sourceware.org> (raw)
In-Reply-To: <bug-17311-682@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from Ralf dot Wildenhues at gmx dot de 2006-02-07 17:43 -------
(In reply to comment #22)
> - Do there exist directories in the GCC build tree where both libtool-created
> and non-libtool-created libraries are (possibly) built?
>
> That is THE KEY question. The executable in question is lt-gij:
>
> hjl@gnu-13 .libs]$ readelf -d
> /export/build/gnu/gcc/build-x86_64-linux/x86_64-unknown-linux-gnu/libjava/.libs/lt-gij
> | grep RPATH
> 0x000000000000000f (RPATH) Library rpath:
> [/export/build/gnu/gcc/build-x86_64-linux/x86_64-unknown-linux-gnu/libjava/.libs]
> [hjl@gnu-13 .libs]$
>
> libgcc_s.so.1 isn't built by libtool.
Yes, but the one is $stage/gcc/libgcc_s.so.1 and the other is
$stage/x86_64-unknown-linux-gnu/libjava/lib/libgcj.la, so they are built
in different directories.
Libtool has to know that $stage/gcc is something that is necessary for the
uninstalled link and run paths; but libtool also needs to be able to deduce
that the path $stage/gcc must not be used for any installed libraries or
programs.
Now, if I want to fix this properly (in Libtool), then I need to know whether
above question can be answered with yes not only for libgcc_s/libgcj,
but for each library created in GCC. And also the other questions, really.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17311
next prev parent reply other threads:[~2006-02-07 17:43 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
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 [this message]
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=20060207174345.21229.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).