On Thu, 7 Jul 2022 10:18:15 GMT, Magnus Ihse Bursie wrote:
> I don't get it, you are saying that in mainline you get no warning but with
> your patch you get a warning, and yet you claim behavior is the same?
>
> On one hand, it seems like the latter behavior is indeed more correct, if you
> p
On Tue, 5 Jul 2022 03:07:10 GMT, Yasumasa Suenaga wrote:
>> configure failed as following when I run it on WSL 1.
>>
>>
>> checking for version string... 20-internal-adhoc.yasuenag.jdk
>> configure: Found potential Boot JDK using configure arguments
>> configure: The command for java_to_test, w
On Wed, 6 Jul 2022 17:47:21 GMT, Magnus Ihse Bursie wrote:
> I'm worried that with the patch you are proposing, we will unconditinonally
> add `.exe` to any path that is not existing, which will make the next test
> fail (since then the path with the addition of `.exe` will most likely not
> e
On Tue, 5 Jul 2022 03:07:10 GMT, Yasumasa Suenaga wrote:
>> configure failed as following when I run it on WSL 1.
>>
>>
>> checking for version string... 20-internal-adhoc.yasuenag.jdk
>> configure: Found potential Boot JDK using configure arguments
>> configure: The command for java_to_test, w
On Tue, 5 Jul 2022 03:07:10 GMT, Yasumasa Suenaga wrote:
>> configure failed as following when I run it on WSL 1.
>>
>>
>> checking for version string... 20-internal-adhoc.yasuenag.jdk
>> configure: Found potential Boot JDK using configure arguments
>> configure: The command for java_to_test, w
> configure failed as following when I run it on WSL 1.
>
>
> checking for version string... 20-internal-adhoc.yasuenag.jdk
> configure: Found potential Boot JDK using configure arguments
> configure: The command for java_to_test, which resolves as
> "/mnt/d/java/jdk-18/bin/java", can not be fou
