problems using --enable-native-access
Thomas Watson
tjwatson at us.ibm.com
Wed Feb 4 19:58:33 UTC 2026
Try using the JVM option:
-XX:+IgnoreUnrecognizedVMOptions
Tom
________________________________
From: jigsaw-dev <jigsaw-dev-retn at openjdk.org> on behalf of Alan Snyder <javalists at cbfiddle.com>
Sent: Wednesday, February 4, 2026 1:02 PM
To: jigsaw-dev at openjdk.org <jigsaw-dev at openjdk.org>
Subject: [EXTERNAL] problems using --enable-native-access
I started trying to use —enable-native-access but ran into a problem.
I have some (test) programs that I run with many different JDKs. The problem is that giving —enable-native-access to an old JDK is a fatal error.
Is there some way to perform this configuration that does not crash an older JDK?
A system property, perhaps?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jigsaw-dev/attachments/20260204/f8f3a947/attachment.htm>
More information about the jigsaw-dev
mailing list