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/17845] can't build GNU Classpath
Date: Wed, 27 Oct 2004 20:06:00 -0000 [thread overview]
Message-ID: <20041027200617.21293.qmail@sourceware.org> (raw)
In-Reply-To: <20041005154252.17845.tromey@gcc.gnu.org>
------- Additional Comments From mark at gcc dot gnu dot org 2004-10-27 20:06 -------
> Does this mean that you've actually been able to duplicate the bug?
> Can you at least let me have a backtrace?
> Surely it's better to fix the bug than install a workaround in Classpath.
I have seen the bug occur on a cygwin machine to which I don't have access
anymore. I thought it was related to the file system being case-insensitive so
jikes was used to do the source to byte code compilation.
Chris is now seeing it on his powerpc machine.
The workaround at least makes it possible to keep working on GNU Classpath. We
have a policy that GNU Classpath (releases) need to be able to be build with the
latest GCC release (and possibly older versions or CVS).
There isn't a backtrace since it just gives this error messages:
../../classpath/java/security/cert/X509Certificate.java:143: error: Class
`java.security.cert.X509Certificate' can't subclass interface
`java.security.Certificate'.
public abstract class X509Certificate extends Certificate implements
X509Extension
^
../../classpath/java/security/cert/X509Certificate.java:0: confused by earlier
errors, bailing out
Is there a trick to get you the backtrace you need to further analyze why this
is happening?
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |dog at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17845
next prev parent reply other threads:[~2004-10-27 20:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 15:42 [Bug java/17845] New: " tromey at gcc dot gnu dot org
2004-10-05 20:02 ` [Bug java/17845] " pinskia at gcc dot gnu dot org
2004-10-06 9:23 ` aph at gcc dot gnu dot org
2004-10-06 12:05 ` aph at gcc dot gnu dot org
2004-10-06 18:57 ` tromey at gcc dot gnu dot org
2004-10-06 20:31 ` andreast at gcc dot gnu dot org
2004-10-07 10:25 ` aph at gcc dot gnu dot org
2004-10-07 17:46 ` aph at gcc dot gnu dot org
2004-10-11 1:32 ` tromey at gcc dot gnu dot org
2004-10-11 9:11 ` aph at redhat dot com
2004-10-18 16:13 ` aph at gcc dot gnu dot org
2004-10-27 19:08 ` mark at gcc dot gnu dot org
2004-10-27 19:14 ` aph at gcc dot gnu dot org
2004-10-27 20:06 ` mark at gcc dot gnu dot org [this message]
2005-05-01 14:05 ` pinskia at gcc dot gnu dot org
2005-05-01 17:24 ` dog at bluezoo dot org
2005-05-01 17:28 ` pinskia at gcc dot gnu dot org
2005-05-11 11:04 ` [Bug java/17845] [4.1 Regression] More problems with simple type names as superclasses bonzini at gcc dot gnu dot org
2005-05-11 11:05 ` bonzini at gcc dot gnu dot org
2005-05-11 11:06 ` bonzini at gcc dot gnu dot org
2005-05-11 12:19 ` bonzini at gcc dot gnu dot org
2005-05-11 12:25 ` pinskia at gcc dot gnu dot org
2005-05-11 12:31 ` paolo dot bonzini at lu dot unisi dot ch
2005-05-12 8:09 ` bonzini at gcc dot gnu dot org
2005-05-12 14:10 ` bonzini at gcc dot gnu dot org
2005-05-19 11:19 ` bonzini at gcc dot gnu dot org
2005-05-19 11:24 ` cvs-commit at gcc dot gnu dot org
2005-06-05 7:53 ` pinskia at gcc dot gnu dot org
2005-08-17 12:57 ` cvs-commit at gcc dot gnu dot org
2005-08-17 15:16 ` 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=20041027200617.21293.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).