Fails building jruby-9.2.19.0

```
> asdf install ruby jruby-9.2.19.0
Downloading jruby-bin-9.2.19.0.tar.gz...
-> https://dqw8nmjcqpjn7.cloudfront.net/1f74885a2d3fa589fcbeb292a39facf7f86be3eac1ab015e32c65d32acf3f3bf
Installing jruby-9.2.19.0...

BUILD FAILED (Gentoo using ruby-build 20210801)

Inspect or clean up the working tree at /tmp/ruby-build.20220407111437.1019838.N78T1U
Results logged to /tmp/ruby-build.20220407111437.1019838.log

Last 10 log lines:
ETag: "45de731d4859ea873fda5a3a5dd3857a-4"
X-Cache: Hit from cloudfront
Via: 1.1 1be5216f770ec05deb91e9e25b61b898.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: HEL51-P1
X-Amz-Cf-Id: gOqVNHaay51v5mz9jQAFLg93rnJ9Bbh0HMmiZw3aUQTHyu-kSxbu2w==
Age: 29584

/tmp/ruby-build.20220407111437.1019838.N78T1U/jruby-9.2.19.0 /tmp/ruby-build.20220407111437.1019838.N78T1U ~/Documents/test
* run-java-tool was invoked directly
* run-java-tool should only be used via symlinks to it
```

```
> cat /tmp/ruby-build.20220407111437.1019838.log
/tmp/ruby-build.20220407111437.1019838.N78T1U ~/Documents/test
HTTP/1.1 200 OK
Content-Type: binary/octet-stream
Content-Length: 26296142
Connection: keep-alive
Last-Modified: Thu, 15 Jul 2021 18:52:49 GMT
Accept-Ranges: bytes
Server: AmazonS3
Date: Thu, 07 Apr 2022 00:01:34 GMT
ETag: "45de731d4859ea873fda5a3a5dd3857a-4"
X-Cache: Hit from cloudfront
Via: 1.1 1be5216f770ec05deb91e9e25b61b898.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: HEL51-P1
X-Amz-Cf-Id: gOqVNHaay51v5mz9jQAFLg93rnJ9Bbh0HMmiZw3aUQTHyu-kSxbu2w==
Age: 29584

/tmp/ruby-build.20220407111437.1019838.N78T1U/jruby-9.2.19.0 /tmp/ruby-build.20220407111437.1019838.N78T1U ~/Documents/test
* run-java-tool was invoked directly
* run-java-tool should only be used via symlinks to it
```

I don't understand that is wrong, so what should I do with this?

Start by reproducing `asdf install ruby jruby-9.2.19.0` on Gentoo and inspect the generated `/tmp/ruby-build...log` alongside the final `run-java-tool` output. Trace the JRuby installation entry point in the ruby-build integration; done means identifying the cause of the failed build and confirming a successful installation or documenting the required environment change.

Written by the indexing model from the issue text.