Charles Oliver Nutter

Removing the `gnu99` flag allows the Makefile to be generated, but there seems to still be a dependency on `ruby.h` which is not shipped with JRuby: ```diff diff --git a/ext/rbs_extension/extconf.rb...

Ok, looks like there's still quite a few dependencies on the CRuby C API, so perhaps this is premature...

This is a very interesting use case, and one I'd like to work with you to support better! I think part of the correct fix would be to do a...

Looks like it's processing the Java command line arguments and expecting them to be a version number? It picks up your G1 flag and doesn't know how to handle it....

@diguage The line of concern in your sample output is this one: ``` NOTE: Picked up JDK_JAVA_OPTIONS: -Djava.io.tmpdir=/tmp -XX:+PrintCommandLineFlags -XX:ConcGCThreads=3 -XX:G1ConcRefinementThreads=10 -XX:GCDrainStackTargetSize=64 -XX:InitialHeapSize=536870912 -XX:MarkStackSize=4194304 -XX:MaxHeapSize=8589934592 -XX:MinHeapSize=6815736 -XX:+PrintCommandLineFlags -XX:ReservedCodeCacheSize=251658240 -XX:+SegmentedCodeCache -XX:+UseCompressedOops...

I am not sure how those flags would get interpreted by the Maven plugin as being JRuby arguments. It's very peculiar. I'll poke around a bit.

Ok I think I understand what happened here. When `JDK_JAVA_OPTIONS` is set in the env, the JVM itself will warn about it: ``` [] jruby $ jruby -v jruby 10.0.1.0-SNAPSHOT...

Well I have a fix for this, but the test doesn't fail because I can't reproduce the issue. It seems like the `Picked up JDK_JAVA_OPTIONS` line is being output to...

Thank you!

I have duplicated the Dockerfile from the other releases for 10-snapshot based on the latest build and it appears to work properly: ``` [] docker-jruby $ cd 10/jdk21 [] jdk21...