Problem with JVMCI on Cygwin

Gilles Duboscq gilles.m.duboscq at
Thu Mar 2 13:59:54 UTC 2017

Hi Russ,

When building on Windows, it's probably better not to use Cygwin.
When running on cygwin, mx tries to use some kind of hybrid mode where we run on cygwin (unix-ish) but target Windows for the JVMCI build. That's very fragile/hacky.

Could you try running in a normal windows environment (make sure you use Windows python, not cygwin python)?

Unfortunately we have not been testing on windows for a long time so it's likely that windows support has bit-rotten in both mx and graal-jvmci-8.


On 02/03/17 14:33, Russ Powers wrote:
> Hello,
> I've managed to build JVMCI on Cygwin, and the
> jdk1.8.0_121\product\jre\bin\server
> directory contains the built jvm.dll and jvm.pdb.  However, when I try
> using mx on graal-core (with the proper JAVA_HOME set), it gives me this
> error:
> The VM does not support the minimum JVMCI API version required by Graal.
> Cannot read JVMCI version from java.vm.version property: 25.71-b01-internal.
> Set the JVMCI_VERSION_CHECK environment variable to "ignore" to suppress
> this error or to "warn" to emit a warning and continue execution.
> Currently used Java home directory is c:\proj\graal\tools\graal-
> jvmci-8\jdk1.8.0_121\product\jre.
> It looks like the JVMCI info is missing, and when I run ./java -version, it
> doesn't contain the JVMCI info either.  I checked, and it's definitely
> using the newly built jvm.dll.  Is there something else I should be doing
> here?  I'm stumped.  Thanks in advance.
> Russ

More information about the graal-dev mailing list