public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/12001] _Jv_FindClass dumps core when Oracle's classes12.zip in $CLASSPATH Date: Wed, 14 Jan 2004 17:27:00 -0000 [thread overview] Message-ID: <20040114172700.5205.qmail@sources.redhat.com> (raw) In-Reply-To: <20030821012448.12001.nbryant@allegientsystems.com> ------- Additional Comments From tromey at gcc dot gnu dot org 2004-01-14 17:26 ------- I'm retargeting back to 3.4.0. The patch is still pending, I just haven't looked at it yet. I did go looking for the Oracle zip file yesterday but didn't want to make an account for myself to download it. But I guess I'll bite the bullet and do that. Reworking the patch to avoid the API problem is no trouble. I can easily do that at patch-application time. Sorry this has been delayed so long. BTW, Andrew, sometimes libgcj bug reports aren't looked at for a long time. I don't think this is a good reason to retarget them away from 3.4. We've had some trouble getting people scheduled to work on 3.4 bugs, but it will happen. I think we can always declare these bugs "won't be fixed" at some later date -- there's no particular rush to do that IMO. -- What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.5.0 |3.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12001
next prev parent reply other threads:[~2004-01-14 17:27 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-21 1:24 [Bug libgcj/12001] New: " nbryant at allegientsystems dot com 2003-08-21 1:32 ` [Bug libgcj/12001] " pinskia at gcc dot gnu dot org 2003-08-21 2:15 ` nbryant at allegientsystems dot com 2003-08-21 3:25 ` tromey at gcc dot gnu dot org 2003-08-21 4:28 ` nbryant at allegientsystems dot com 2003-08-21 5:54 ` nbryant at allegientsystems dot com 2003-08-23 1:26 ` dhazeghi at yahoo dot com 2003-12-02 18:51 ` pinskia at gcc dot gnu dot org 2003-12-02 18:58 ` nbryant at allegientsystems dot com 2003-12-02 19:02 ` pinskia at gcc dot gnu dot org 2004-01-14 3:15 ` pinskia at gcc dot gnu dot org 2004-01-14 3:20 ` nbryant at allegientsystems dot com 2004-01-14 17:27 ` tromey at gcc dot gnu dot org [this message] 2004-01-14 21:49 ` tromey at gcc dot gnu dot org 2004-01-14 22:08 ` tromey at gcc dot gnu dot org 2004-01-14 22:27 ` nbryant at allegientsystems dot com 2004-01-14 22:42 ` nbryant at allegientsystems dot com 2004-01-14 22:50 ` cvs-commit at gcc dot gnu dot org 2004-01-14 22:51 ` tromey 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=20040114172700.5205.qmail@sources.redhat.com \ --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: linkBe 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).