From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Dr Andrew John Hughes <gnu_andrew@member.fsf.org>
Cc: java@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: gcj fails to compile java
Date: Tue, 28 Sep 2010 20:35:00 -0000 [thread overview]
Message-ID: <20100928203548.GA7620@bromo.med.uc.edu> (raw)
In-Reply-To: <AANLkTi=QNATvOu6E19EH7CUwBaj4xmboUf0HgdXFMbG+@mail.gmail.com>
On Tue, Sep 28, 2010 at 08:21:45PM +0100, Dr Andrew John Hughes wrote:
> On 25 September 2010 14:20, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
> > I've filed PR45773 concerning the new regression in gcj where java classes can
> > no longer be compiled with ecj.jar. Since r163770 (with r163814 backported to fix
> > the libjava build), any attempt to compile a java source file with gcj produces
> > the error...
> >
> > gcj --main=testme -O testme.java
> > Exception in thread "main" java.lang.NoClassDefFoundError: org.eclipse.jdt.internal.compiler.batch.GCCMain
> > at gnu.java.lang.MainThread.run(libgcj.12.dylib)
> > Caused by: java.lang.ClassNotFoundException: org.eclipse.jdt.internal.compiler.batch.GCCMain not found in gnu.gcj.runtime.SystemClassLoader{urls=[file:/sw/share/java/ecj/ecj.jar,file:./], parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
> > at java.net.URLClassLoader.findClass(libgcj.12.dylib)
> > at java.lang.ClassLoader.loadClass(libgcj.12.dylib)
> > at java.lang.ClassLoader.loadClass(libgcj.12.dylib)
> > at gnu.java.lang.MainThread.run(libgcj.12.dylib)
> >
> > This problem does not exist at r163768. I am reposting this problem since the new
> > bugzilla keeps reporting...
> >
> > GCC Bugzilla has suffered an internal error. Please save this page and send it to dberlin@gcc.gnu.org with details of what you were doing at the time this message appeared.
> >
> > URL: file:///Users/howarth/Internal Error.html
> >
> > There was an error sending mail from '"howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>' to 'java-prs@gcc.gnu.org':Can't send data
> >
> > whenever I add new information and nothing appears in the gcc-bugs archives from those sessions
> > (although the PR itself if updated).
> > Jack
> >
>
> With a simple HelloWorld class:
>
> $ cat HelloWorld.java
> public class HelloWorld
> {
> public static void main(String[] args) { System.out.println("Hello World!"); }
> }
>
> current HEAD works fine for me:
Of course it does because the bug was just fixed...
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45773#c20
>
> $ /home/andrew/build/gcj/bin/gcj --main=HelloWorld -O HelloWorld.java
> $ LD_LIBRARY_PATH=/home/andrew/build/gcj/lib64 ./a.out
> Hello World!
> $ /home/andrew/build/gcj/bin/gcj --version
> gcj (GCC) 4.6.0 20100928 (experimental) [trunk revision 164689]
>
> Can you attach the testme.java file?
> --
> Andrew :-)
>
> Free Java Software Engineer
> Red Hat, Inc. (http://www.redhat.com)
>
> Support Free Java!
> Contribute to GNU Classpath and the OpenJDK
> http://www.gnu.org/software/classpath
> http://openjdk.java.net
>
> PGP Key: 94EFD9D8 (http://subkeys.pgp.net)
> Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8
prev parent reply other threads:[~2010-09-28 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 13:20 Jack Howarth
2010-09-28 19:21 ` Dr Andrew John Hughes
2010-09-28 20:35 ` Jack Howarth [this message]
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=20100928203548.GA7620@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=gnu_andrew@member.fsf.org \
--cc=java@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).