official compiler for Solaris jdk9 build?

[Erik Joelsson]

Actually, we might have issues in configure if the standard headers 
aren't available on the system. At least I have not tested that scenario 
and I can imagine that our SYSROOT_CFLAGS aren't always used in the 
configure tests. This is of course a bug, but a workaround would be to 
have the system headers installed on the system. They won't be used 
during the actual build.

/Erik

On 2015-06-05 15:05, Magnus Ihse Bursie wrote:
> Did you use the --with-devkit option?
>
> /Magnus
>
>> 5 jun 2015 kl. 10:47 skrev Semyon Sadetsky <semyon.sadetsky at oracle.com>:
>>
>> Hi,
>>
>> I have installed the devkit on clean Solaris 11.2 instance but configure fails because compiler cannot find the includes path:
>> c -o conftest    conftest.c  >&5
>> "conftest.c", line 9: cannot find include file: <stdio.h>
>> "conftest.c", line 13: undefined symbol: FILE
>>
>> though devkit & sysroot path was detected by configure.
>> Any reasons why?
>> I did not not install normal solaris studio only the devkit.
>>
>> Thank you.
>> --Semyon
>>
>>
>>> On 6/3/2015 11:38 AM, Semyon Sadetsky wrote:
>>>
>>>> On 6/3/2015 11:28 AM, Magnus Ihse Bursie wrote:
>>>>> On 2015-06-02 17:27, Semyon Sadetsky wrote:
>>>>> Hi,
>>>>>
>>>>> I'm trying to build jdk9 under the current Solaris 11.2 version.
>>>>> Which version of the Solaris Studio should be installed for that? The readme-builds states:
>>>>> ...
>>>>> At a minimum, the Studio 12 Update 1 Compilers (containing version 5.10 of the C and C++ compilers) is required, including specific patches.
>>>>> ...
>>>>> Currently there are 3 versions currently available for downloading:
>>>>>
>>>>> Oracle Solaris Studio 12.2
>>>>> Oracle Solaris Studio 12.3
>>>>> Oracle Solaris Studio 12.4
>>>>>
>>>>> I tried all 3 and only with 12.3 I do no receive build warnings about wrong compiler version,
>>>>> but my build constantly fails with 12.3 with the next message:
>>>>>
>>>>> Compiling 246 files for jdk.jdi
>>>>> "/jdk9/client/jdk/src/java.base/unix/native/libjava/childproc.c", line 384: warning: statement not reached (E_STATEMENT_NOT_REACHED)
>>>>> "/jdk9/client/jdk/src/java.base/unix/native/libjli/java_md_solinux.c", line 496: warning: statement not reached (E_STATEMENT_NOT_REACHED)
>>>>> ld: fatal: file /jdk9/client/build/solaris-x86_64-normal-server-fastdebug/support/modules_libs/java.base/amd64/server/libjvm.so: not an ELF object
>>>>> gmake[3]: *** [/jdk9/client/build/solaris-x86_64-normal-server-fastdebug/support/modules_libs/java.base/amd64/libverify.so] Error 2
>>>>> gmake[3]: *** Waiting for unfinished jobs....
>>>>> gmake[2]: *** [java.base-libs] Error 1
>>>>>
>>>>> Even --disable-warnings-as-errors option does not save the build from failure.
>>>> That's because the warning does not cause the build failure. Read the logs again. :-)
>>>>
>>>> The real error here is "libjvm.so: not an ELF object" which causes the linking to fail for libverify.so. The warning from libjava is just a red herring.
>>>>
>>>> Your hotspot build is broken. Try
>>>> "make clean-hotspot"
>>>> "make hotspot"
>>>> and see if you spot any errors. Otherwise you'd probably just left the build in a bad state.
>>>>
>>>> /Magnus
>>> Thank you. In reality it was even worse when I add the option disabling warnings as errors the VM hangs in the middle of the build and those messages I got after restarting it and running the incremental build. This scenario was reproduced 2 times with clean build. So, my next attempt is a clean install with devkits.
>>>
>>> --Semyon
>>>
>>>>> Could you send me the software list with the versions that should be installed on a clean Solaris 11.2 instance to have the build running smoothly?
>>>>>
>>>>> Thank you,
>>>>> --Semyon