This is the mail archive of the
kawa@sources.redhat.com
mailing list for the Kawa project.
Re: Differences between Unix and Windows Kawa?
- To: Jocelyn Paine <popx at pop3 dot ifs dot org dot uk>
- Subject: Re: Differences between Unix and Windows Kawa?
- From: Andrew Smith <asmith at wpequity dot com>
- Date: 29 Aug 2001 11:28:46 -0400
- Cc: Per Bothner <per at bothner dot com>, kawa at sourceware dot cygnus dot com
- References: <AB2EBFA5D38F1AA785256AB6001C2B35.001C2B6A85256AB6@wpequity.com>
What version of the JDK are you using to compile with?
There is a bug in an earlier version of javac that causes this exception
to be thrown if an inner class calls a private method on an outer class
that then invokes another private method.
Take a look at bug #4172371 at java.sun.com's bug parade.
-a.
On Tue, 2001-08-28 at 01:07, Jocelyn Paine wrote:
>
>
> I'll do that. I was quite careful about the FTP modes though, so I don't
> think it is file corruption. Just now, I tried copying just the new
> ModuleExp.class from the Unix machine and inserting it into the original
> distributed 1.6.94 jar file on the Windows one. A jar t listing shows that
> it's in there in the correct location, but this time, when I tried running
> Kawa from the amended jar, it returned immediately to DOS: no messages.
> It's quite puzzling.
>
> Jocelyn Paine
> http://www.ifs.org.uk/~popx/
> +44 (0)7768 534 091
>
>
> On Mon, 27 Aug 2001, Per Bothner wrote:
>
> > Jocelyn Paine wrote:
> >
> > >I just tried remaking Kawa 1.6.94 on my Unix machine (with Per's
> ModuleExp
> > >patch), and then copied the jar files to the machine I use for Windows,
> > >this being easier than redoing the remake under Windows. Except that it
> > >didn't work. Running kawa.repl -w from the newly-made files failed under
> > >Windows:
> > > java.lang.VerifyError: Class gnu/expr/ErrorExp overrides final method
> > > print.(Ljava/io/PrintWriter;)V
> > > at kawa.lang.Translator.<clinit>(Translator.java:52)
> > >
> > Well. my first guess is file corruption, perhaps because it was copied as
> a
> > text file (the default when using ftp) rather than a binary file.
> >
> > You can use javap or 'java gnu.bytecode.dump' to dump the contents of a
> > class
> > file. Do that to look at the actual final flag. (You might need to use
> > the jar tool
> > to extract ErrorExp.class.)
> >
> >
>