From: Jakub Jelinek <jakub@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix linking with -findirect-dispatch
Date: Tue, 16 Apr 2013 10:26:00 -0000 [thread overview]
Message-ID: <20130416102601.GQ12880@tucnak.redhat.com> (raw)
In-Reply-To: <mvmd2tuu6o5.fsf@hawking.suse.de>
On Tue, Apr 16, 2013 at 12:11:06PM +0200, Andreas Schwab wrote:
> Jakub Jelinek <jakub@redhat.com> writes:
>
> > $ readelf -Wa libjava/.libs/libgcj_bc.so
>
> That's not the installed library.
If that isn't the installed library, then the bug is that it isn't
installed. Our spec file reshuffles libraries around heavily, so perhaps
the upstream Makefiles are buggy and the reshuffling just hides the bug,
but your patch isn't a fix.
Installed */libgcj_bc.so should be a copy of the dummy library
*/libjava/.libs/libgcj_bc.so, and */libgcj_bc.so.1.0.0 should be
a (relinked?) copy of the dummy library */libjava/.libs/libgcj_bc.so.1.0.0.
I'm pretty sure when the changes were added for gcc 4.2 it worked just fine,
but as our rpms don't use what this installs, it is possible it got broken
later on.
Jakub
next prev parent reply other threads:[~2013-04-16 10:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 8:36 Andreas Schwab
2013-04-16 8:39 ` Jakub Jelinek
2013-04-16 8:59 ` Bryce McKinlay
2013-04-16 9:13 ` Andreas Schwab
2013-04-16 9:19 ` Jakub Jelinek
2013-04-16 9:37 ` Andreas Schwab
2013-04-16 9:49 ` Jakub Jelinek
2013-04-16 9:55 ` Matthias Klose
2013-04-26 11:22 ` Matthias Klose
2013-04-26 11:50 ` Andrew Haley
2013-04-16 9:57 ` Andreas Schwab
2013-04-16 10:08 ` Jakub Jelinek
2013-04-16 10:11 ` Andreas Schwab
2013-04-16 10:26 ` Jakub Jelinek [this message]
2013-04-16 10:31 ` Andreas Schwab
2013-04-16 16:13 ` Andreas Schwab
2013-04-16 16:19 ` Jakub Jelinek
2013-04-16 17:22 ` Andreas Schwab
2013-06-03 10:56 ` Andreas Schwab
2013-04-16 16:39 ` Bryce McKinlay
2013-04-17 13:17 ` Andreas Schwab
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=20130416102601.GQ12880@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=schwab@suse.de \
/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).