public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/20160] [4.0 Regression] link errors building libgcj tests Date: Thu, 24 Feb 2005 16:04:00 -0000 [thread overview] Message-ID: <20050224131932.3388.qmail@sourceware.org> (raw) In-Reply-To: <20050223105204.20160.rearnsha@gcc.gnu.org> ------- Additional Comments From rearnsha at gcc dot gnu dot org 2005-02-24 13:19 ------- Yes, that's the patch that introduces the problem. -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-02-24 13:19:31 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20160
next prev parent reply other threads:[~2005-02-24 13:19 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-23 15:11 [Bug libgcj/20160] New: " rearnsha at gcc dot gnu dot org 2005-02-23 15:11 ` [Bug libgcj/20160] " rmathew at gcc dot gnu dot org 2005-02-24 16:04 ` rearnsha at gcc dot gnu dot org [this message] 2005-02-24 16:24 ` rearnsha at gcc dot gnu dot org 2005-02-24 17:09 ` rearnsha at gcc dot gnu dot org 2005-02-25 2:41 ` rth at gcc dot gnu dot org 2005-02-25 2:58 ` rth at gcc dot gnu dot org 2005-02-25 6:40 ` aoliva at gcc dot gnu dot org 2005-02-25 6:49 ` aoliva at gcc dot gnu dot org 2005-02-25 16:22 ` aoliva at gcc dot gnu dot org 2005-02-25 19:00 ` rearnsha at gcc dot gnu dot org 2005-02-25 23:25 ` aoliva at gcc dot gnu dot org 2005-02-27 6:03 ` [Bug libgcj/20160] [4.0/4.1 " rearnsha at gcc dot gnu dot org 2005-03-01 22:27 ` aoliva at redhat dot com 2005-03-01 22:28 ` cvs-commit at gcc dot gnu dot org 2005-03-01 22:29 ` cvs-commit at gcc dot gnu dot org 2005-03-02 0:27 ` pinskia 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=20050224131932.3388.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: 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).