Configuration script unable to detect boot JDK's modules support

[Erik Joelsson]

Yes, we do, if you don't mind.

/Erik

On 2016-04-02 13:38, Filipp Zhinkin wrote:
> Hi Erik, thanks for reply.
>
> Do we need a JBS's ticket to track this issue?
>
> Thanks,
> Filipp.
>
> On Thu, Mar 31, 2016 at 5:23 PM, Erik Joelsson <erik.joelsson at oracle.com> wrote:
>> It seems the test is indeed incorrect at this point. When I added that test,
>> the launcher would accept just -Xpatch:. It seems to now accept -Xpatch:foo
>> so perhaps we should use that for the test.
>>
>> /Erik
>>
>>
>> On 2016-03-31 09:56, Filipp Zhinkin wrote:
>>> Hi all,
>>>
>>> I'm trying to build OpenJDK from latest sources using JDK9-b111 as a boot
>>> JDK
>>> and configuration script is not able to detect modules support:
>>>
>>> $ bash configure --enable-option-checking=fatal
>>> --with-jvm-variants=server --with-debug-level=release
>>> --disable-headful --with-boot-jdk=/home/filipp/Downloads/bootdir/jdk-9
>>> --with-jtreg=/home/filipp/Development/openjdk/jtreg
>>> ...
>>> $ grep modules build/linux-x86_64-normal-server-release/configure.log
>>> checking if Boot JDK supports modules... no
>>>
>>> I've looked into common/autoconf/boot-jdk.m4 to find out how modules
>>> support is detected and we simply pass '-Xpatch:' to JVM [1]:
>>>
>>> jdk-9/bin/java -Xpatch: -version
>>> Bad value for -Xpatch.
>>> Error: Could not create the Java Virtual Machine.
>>> Error: A fatal exception has occurred. Program will exit.
>>>
>>> Am I missing something or that check should actually pass
>>> -Xpatch:blablabla?
>>>
>>> Regards,
>>> Filipp.
>>>
>>> [1]
>>> http://hg.openjdk.java.net/jdk9/jdk9/file/03543a758cd5/common/autoconf/boot-jdk.m4#l308
>>