From: Tom Tromey <tromey@redhat.com>
To: Paul Nasrat <pauln@truemesh.com>
Cc: eclipse@sources.redhat.com
Subject: Re: Successfull build on rawhide
Date: Tue, 24 Feb 2004 17:25:00 -0000 [thread overview]
Message-ID: <87y8qs5rhu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20040223114134.GC9822@raq465.uk2net.com>
>>>>> "Paul" == Paul Nasrat <pauln@truemesh.com> writes:
Paul> JarWriter fails (see eclipse-jar.out)
Paul> IIRC both these failures doenot terminate build.
In most places we've changed the eclipse build to actually fail on
error. Occasionally we've missed one. Hmm, maybe we made this
change after the snapshot you're using.
Paul> [exec] org/eclipse/jdt/ui/jarpackager/JarWriter.java:112: error: might transfer control into subroutine
This is a bug in gcj's bytecode verifier. For gcc-ssa we just
commented out the error message. That's not really a patch we could
put in the upstream gcj, though.
It is safe to disable compilation of any .jar file, however. Just
edit gcjBuild and tell it not to build this one. The only
ramification is that execution of this code will be a bit slower.
Too bad you missed FOSDEM, we talked extensively about our plans for
gcj and how they will affect this stuff :-). For the verifier my plan
is to put the libgcj verifier into gcj as well, as it is built on a
more hackable (and less buggy) foundation.
Tom
next prev parent reply other threads:[~2004-02-24 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 10:00 Paul Nasrat
2004-02-22 12:20 ` Paul Nasrat
2004-02-22 22:43 ` Paul Nasrat
2004-02-23 11:30 ` Paul Nasrat
2004-02-23 17:46 ` keiths
2004-02-24 17:25 ` Tom Tromey [this message]
2004-02-24 17:21 ` Tom Tromey
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=87y8qs5rhu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eclipse@sources.redhat.com \
--cc=pauln@truemesh.com \
/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).