official compiler for Solaris jdk9 build?
semyon.sadetsky at oracle.com
Fri Jun 5 08:47:18 UTC 2015
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.
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:
>>> 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
>>> 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
>>> line 384: warning: statement not reached (E_STATEMENT_NOT_REACHED)
>>> line 496: warning: statement not reached (E_STATEMENT_NOT_REACHED)
>>> ld: fatal: file
>>> not an ELF object
>>> gmake: ***
>>> Error 2
>>> gmake: *** Waiting for unfinished jobs....
>>> gmake: *** [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.
> 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.
>>> 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
>>> Thank you,
More information about the build-dev