This is the mail archive of the
mailing list for the Cygwin project.
Re: Problem with JVM 1.4.2 on Cygwin 1.5.5-1 on XP and 2000
- From: Moy Easwaran <easwarm at nationwide dot com>
- To: cygwin at cygwin dot com
- Cc: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- Date: Fri, 09 Jan 2004 17:21:05 -0500
- Subject: Re: Problem with JVM 1.4.2 on Cygwin 1.5.5-1 on XP and 2000
Igor Pechtchanski wrote:
> Technically, since you're using -mno-cygwin, this is not a Cygwin
Thanks for the quick reply, Igor. You're right: it doesn't seem like
a cygwin problem at all; more like a problem talking to Sun's jvm.dll
(which was presumably built with MSVC), but (a) I'm using the Cygwin
toolkit to built it, and (b) I figured I'd get better advice on the
Cygwin lists because of the expertise talking to Microsoft- and
related objects "from outside."
> Where is this jvm.dll coming from?
From Sun's Java SDK (http://java.sun.com/j2se/1.4.1/download.html).
$ which jvm.dll java.dll
> > EXPORTS
> > JNI_CreateJavaVM@12
> Are you sure you got the right argument patterns here (i.e., numbers
> the '@' sign)? That may be one source of the problem.
I just copied it straight from inonit.com (and it worked on NT 4.0 and
XP Home). And JNI_CreateJavaVM takes three pointers as arguments
(which is what the patterns denote, right?), so 12 bytes seems right.
> > options.optionString = "-Djava.class.path=c:\\test";
> Shouldn't this also contain a pointer to the default class libraries?
Shouldn't it know where the defaults are? And if they're necessary
then it shouldn't work on NT or XP-Home either.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html