On 2/06/2015 5:54 PM, Semyon Sadetsky wrote:
On 6/2/2015 9:27 AM, David Holmes wrote:
On 2/06/2015 4:20 PM, Semyon Sadetsky wrote:
On 6/2/2015 2:35 AM, Magnus Ihse Bursie wrote:
On 2015-06-01 21:17, Semyon Sadetsky wrote:
Hello,
Could you help me to resolve 9 build problem on Solaris 11.2:
/usr/ccs/bin/nm: solaris_x86_64.o: No such file or directory
gmake[8]: *** [libjvm.so] Error 1
gmake[8]: Leaving directory
`/jdk9/client/build/solaris-x86_64-normal-server-fastdebug/hotspot/solaris_amd64_compiler2/fastdebug'
gmake[7]: *** [the_vm] Error 2
gmake[7]: Leaving directory
`/jdk9/client/build/solaris-x86_64-normal-server-fastdebug/hotspot/solaris_amd64_compiler2/fastdebug'
and earlier in the log:
Assembling
/jdk9/client/hotspot/src/os_cpu/solaris_x86/vm/solaris_x86_64.s
rm -f solaris_x86_64.o
xarch=amd64 -o solaris_x86_64.o
/jdk9/client/hotspot/src/os_cpu/solaris_x86/vm/solaris_x86_64.s
/usr/bin/bash: -o: command not found
gmake[8]: [solaris_x86_64.o] Error 127 (ignored)
Compiling /jdk9/client/hotspot/src/share/vm/gc/shared/space.cpp
rm -f space.o
/opt/solarisstudio12.3/bin/CC -DSOLARIS -DSPARC_WORKS -
...
I guess there should be cc before xarch, but it's omited.
I'm guessing that .s is an assembly file, so most likely it is $(AS)
that resolves to empty. Can you check your spec.gmk for the value of
AS?
/Magnus
Yes, AS was empty.
That suggests something is not set correctly.
after I set it to /opt/solarisstudio12.3/bin/cc the first error message
has gone but then I got:
cc: Warning: -xarch=amd64 is deprecated, use -m64 to create 64-bit
programs
ld: fatal: file solaris_x86_64.o: not an ELF object
gmake[8]: *** [solaris_x86_64.o] Error 2
gmake[8]: *** Waiting for unfinished jobs....
what does cc -V show? The make logic is looking 5.9 or greater to use
the new -m64 option.
David
-----
dev@solaris1:/jdk9/client$ /opt/solarisstudio12.3/bin/cc -V
cc: Sun C 5.12 SunOS_i386 2011/11/16
Then something else must be going wrong that prevents the version check
from being executed successfully. If you configure with LOG_LEVEL=debug
does the build log show any missing commands etc prior to the error above?
There's obviously something generally wrong with your setup based on the
AS problem.
David
I have also solaris studio 12.4 installed in this VM but it is in
another dir and not on the path.
