From: "Phil Shaw" <phil@mkdoc.com>
To: rhug-rhats@sources.redhat.com
Subject: Common issues adapting to GCJ
Date: Wed, 17 Nov 2004 12:41:00 -0000 [thread overview]
Message-ID: <419B46F8.15941.56609AB@localhost> (raw)
I have come across a couple of known bugs in GCJ as I have been
incorporating some open source systems into a project I am working
on. I was wondering if this group has a "top 10 issues" and their
symptoms guide?
Could members pitch-in their most common gripes?
I'm currently scratching my head over an IncompatibleClassChangeError
with the java.lang.reflect.Constructor newInstance method. I'll let
you know how it turns out.
Before I learned of this project I made a couple of workarounds for
GCJ bug 9866 in JTidy. If anyone's interested I can pass on the
changes.
Best regards,
Phil
reply other threads:[~2004-11-17 12:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=419B46F8.15941.56609AB@localhost \
--to=phil@mkdoc.com \
--cc=rhug-rhats@sources.redhat.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).