public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aph at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/37068] [4.4 Regression] libgcj linkage failure: Incorrect library ABI version detected
Date: Tue, 04 Nov 2008 23:08:00 -0000 [thread overview]
Message-ID: <20081104230635.17362.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37068-276@http.gcc.gnu.org/bugzilla/>
------- Comment #31 from aph at redhat dot com 2008-11-04 23:06 -------
Subject: Re: [4.4 Regression] libgcj linkage failure: Incorrect
library ABI version detected
dave at hiauly1 dot hia dot nrc dot ca wrote:
> ------- Comment #30 from dave at hiauly1 dot hia dot nrc dot ca 2008-11-04 19:01 -------
> Subject: Re: [4.4 Regression] libgcj linkage failure: Incorrect library ABI
> version detected
>
>> That error now is gone, but we may only have stepped to the next error on these
>> platforms. We can decide if it should continue in this bug or a new bug should
>> be opened.
>
> If the error is releated to the running of constructors for class
> registration or resource registration, then I think we should continue
> with this bug. Otherwise, it's a new bug.
OK, but I need to know if my patch has been tested well enough for
me to check it in. I'm fairly certain it doesn't break x86 GNU/Linux.
Andrew.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37068
next prev parent reply other threads:[~2008-11-04 23:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 14:59 [Bug java/37068] New: " danglin at gcc dot gnu dot org
2008-08-10 19:56 ` [Bug java/37068] " pinskia at gcc dot gnu dot org
2008-08-22 15:23 ` rguenth at gcc dot gnu dot org
2008-09-09 12:56 ` hubicka at gcc dot gnu dot org
2008-10-16 20:13 ` dje at gcc dot gnu dot org
2008-10-30 23:30 ` dave at hiauly1 dot hia dot nrc dot ca
2008-10-31 4:24 ` dave at hiauly1 dot hia dot nrc dot ca
2008-10-31 17:20 ` ro at gcc dot gnu dot org
2008-10-31 19:51 ` dave at hiauly1 dot hia dot nrc dot ca
2008-10-31 23:32 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-01 16:20 ` danglin at gcc dot gnu dot org
2008-11-01 16:51 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-02 2:34 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-03 10:19 ` aph at gcc dot gnu dot org
2008-11-03 11:55 ` jakub at gcc dot gnu dot org
2008-11-03 14:29 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-03 14:47 ` aph at gcc dot gnu dot org
2008-11-03 14:53 ` jakub at gcc dot gnu dot org
2008-11-03 15:03 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-03 15:13 ` aph at redhat dot com
2008-11-03 17:37 ` dje at gcc dot gnu dot org
2008-11-03 17:40 ` mmitchel at gcc dot gnu dot org
2008-11-03 17:42 ` jakub at gcc dot gnu dot org
2008-11-03 17:49 ` aph at gcc dot gnu dot org
2008-11-04 5:52 ` mark at codesourcery dot com
2008-11-04 10:33 ` aph at gcc dot gnu dot org
2008-11-04 16:10 ` aph at redhat dot com
2008-11-04 18:12 ` dje dot gcc at gmail dot com
2008-11-04 18:17 ` aph at redhat dot com
2008-11-04 18:17 ` dje dot gcc at gmail dot com
2008-11-04 18:20 ` aph at gcc dot gnu dot org
2008-11-04 18:35 ` dje at gcc dot gnu dot org
2008-11-04 19:02 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-04 23:08 ` aph at redhat dot com [this message]
2008-11-05 1:12 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-05 10:08 ` aph at gcc dot gnu dot org
2008-11-05 10:16 ` jakub at gcc dot gnu dot org
2008-11-05 13:41 ` ro at techfak dot uni-bielefeld dot de
2008-11-05 14:03 ` aph at redhat dot com
2008-11-05 15:09 ` ro at techfak dot uni-bielefeld dot de
2008-11-05 15:47 ` dje at gcc dot gnu 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=20081104230635.17362.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).