In the build-infra world, the compiler has to be found by configure in
some way (usually by putting it in the path) at configure time. After
that the build will use the absolute path found by configure. Configure
will definitely fail if it can't find a valid compiler.
/Erik
On 2012-06-26 11:08, Kelly O'Hair wrote:
Solaris builds will always be tough.
You need particular versions of the C/C++ compilers (cc/CC or Sun Studio, or
now Oracle Solaris Studio) in your PATH.
I'm not sure exactly how this will be dealt with in the new build
infrastructure yet. But I'll be looking at it today hopefully.
-kto
On Jun 22, 2012, at 5:15 PM, Jonathan Gibbons wrote:
I was doing a top level build, which complained about a few things until I
fixed them up. But then the check seemed to be OK and the build proceeded OK,
until it ran into this issue, and then another issue -- something that was
brought in from /usr/sfw because of the default setting to enable debug
symbols. Once I figured out how to disable them, I finally got a build to
proceed.
I presume the new build system will be better at determining up front
everything that will be needed during the build.
-- Jon
On 06/22/2012 05:02 PM, David Holmes wrote:
Hi Jon,
On 23/06/2012 5:16 AM, Jonathan Gibbons wrote:
A build of tl passed "make sanity" but I still got this error:
CC -DSOLARIS -DSPARC_WORKS -DIA32
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/share/vm/prims
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/share/vm
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/share/vm/precompiled
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/cpu/x86/vm
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/os_cpu/solaris_x86/vm
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/os/solaris/vm
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/os/posix/vm
-I/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/share/vm/adlc
-I../generated -DASSERT -DTARGET_OS_FAMILY_solaris -DTARGET_ARCH_x86
-DTARGET_ARCH_MODEL_x86_32 -DTARGET_OS_ARCH_solaris_x86
-DTARGET_OS_ARCH_MODEL_solaris_x86_32 -DTARGET_COMPILER_sparcWorks
-DCOMPILER2 -DCOMPILER1 -DDONT_USE_PRECOMPILED_HEADER -D_REENTRANT
-library=Cstd -g -xwe -g -c -o ../generated/adfiles/adlparse.o
/tmp/jjg/7178763-doctree-oome/tl/hotspot/src/share/vm/adlc/adlparse.cpp
make381[6]: CC: Command not found
Was this a JDK sanity check or hotspot? hotspot doesn't really do any sanity
checking of its own. What did the sanity check report?
David
-----
make381[6]: *** [../generated/adfiles/adlparse.o] Error 127
make381[6]: Leaving directory
`/tmp/jjg/7178763-doctree-oome/tl/build/solaris-i586/hotspot/outputdir/solaris_i486_compiler2/product'
make381[5]: *** [ad_stuff] Error 2
make381[5]: Leaving directory
`/tmp/jjg/7178763-doctree-oome/tl/build/solaris-i586/hotspot/outputdir/solaris_i486_compiler2/product'
make381[4]: *** [product] Error 2
make381[4]: Leaving directory
`/tmp/jjg/7178763-doctree-oome/tl/build/solaris-i586/hotspot/outputdir'
make381[3]: *** [generic_build2] Error 2
make381[3]: Leaving directory
`/tmp/jjg/7178763-doctree-oome/tl/hotspot/make'
make381[2]: *** [product] Error 2
make381[2]: Leaving directory
`/tmp/jjg/7178763-doctree-oome/tl/hotspot/make'
make381[1]: *** [hotspot-build] Error 2
make381[1]: Leaving directory `/tmp/jjg/7178763-doctree-oome/tl'
make381: *** [build_product_image] Error 2
