public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/21418] Order of source files matters when compiling
Date: Fri, 06 May 2005 14:50:00 -0000 [thread overview]
Message-ID: <20050506145026.2682.qmail@sourceware.org> (raw)
In-Reply-To: <20050506142914.21418.mark@gcc.gnu.org>
------- Additional Comments From mark at gcc dot gnu dot org 2005-05-06 14:50 -------
> I thought I saw something like this before.
You are probably refering to bug #17845 which was recently closed since it
couldn't be reproduced (because I added a workaround to GNU Classpath). I cannot
say with certainty that this is the same bug though. The main difference with
that bug is that we have a testcase here (even though there was another
workaround added to GNU Classpath CVS).
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2005-05-06 14:50:24
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21418
next prev parent reply other threads:[~2005-05-06 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 14:29 [Bug java/21418] New: " mark at gcc dot gnu dot org
2005-05-06 14:31 ` [Bug java/21418] " pinskia at gcc dot gnu dot org
2005-05-06 14:50 ` mark at gcc dot gnu dot org [this message]
2005-05-09 10:03 ` bonzini at gcc dot gnu dot org
2005-05-10 13:55 ` bonzini at gcc dot gnu dot org
2005-09-11 22:29 ` mark at gcc dot gnu dot org
2005-09-11 23:36 ` cvs-commit at developer dot classpath dot org
2005-09-21 9:56 ` rmathew at gcc dot gnu dot org
2005-09-21 13:35 ` cvs-commit at gcc dot gnu dot org
2005-09-21 14:03 ` pinskia at gcc dot gnu dot org
2005-09-21 14:05 ` pinskia at gcc dot gnu dot org
2005-09-22 17:45 ` mckinlay at redhat dot com
2005-10-01 6:49 ` cvs-commit 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=20050506145026.2682.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).