>From shivakumar.gn at gmail.com Mon Sep 17 20:09:43 2007
>[1] In both CCD & SFW, ${SRC}/tools/cc attempts to use
>/ws/onnv-tools/SUNWspro/SS11/bin/cc
>Explicitly setting SPRO_ROOT=/opt/SUNWspro (for my case) corrects
>this. There is a SPRO_VROOT in the respective env.sh provided to
>bldenv, not sure if it was supposed to be SPRO_ROOT.
SPRO_VROOT is correct I think. If you install the compilers normally
(rather than as we have so we can have multiple versions available)
then you just want that to be /opt/SUNWspro, which is the default
installation location.
this actually should match ON. and I think it was tested once
long ago so it should be right :)
>[2] Incase of SFW, ${SRC}/tools/cc sets
>cc=${SPRO_ROOT-/ws/onnv-tools/SUNWspro}/SS11/bin/cc
>
>while in CCD, it sets
>cc=${SPRO_ROOT-/ws/onnv-tools/SUNWspro/SS11}/bin/cc
>
>I believe the one in CCD sources is appropriate.
no... SPRO_ROOT is the top-level directory which has all
the compilers installed - we have that like this:
{mike_s:yavin:64} ls /ws/onnv-tools/SUNWspro
Archives/ SC5.0/ SC6.1-s10/ SOS8/ SS11-old/
README SC5.x/ SC6.2/ SOS8-Beta/ sun4v/
SC2.0.1/ SC6.1/ SOS10/ SOS8-old@
SC4.2/ SC6.1-S9-Beta/ SOS10-OS/ SS11/
SPRO_VROOT includes the version number (like SS11, or more specifically
what the directory containing that version was actually named when
we copied it to /ws/onnv-tools)). While it is a pain that the wrapper
scripts hardcode the number too, I'm not even sure it matters since for
sfw I don't think they are even used. It seems to be used in a few
places in the ccd. They were supposed to be a sneaky way to add
compiler flags to the compiler behind configure's back but I think
folks have just found other ways. Which is fine with me.
Those scripts predate the introduction of SPRO_VROOT and so
don't use it, and as they should probably be removed rather
than enhanced I haven't gone and fixed the sfw ones.
>[3] The observations applies to both cc & CC.
and note CC wouldn't work even if you used it in the ccd.
>I have a query,
>Are all softwares in SFW & CCD built using sunpro only or is gcc/g++
>used.
you could grep the Makefile.sfw's, but I believe gcc is used in a few places.
I think gcc uses it to build itself and nmap uses g++.
>I ask this since tools/gcc & tools/g++ instead of forwarding to
>underlying gcc/g++, have a error message saying "You should be using
>Sun CC" and exit.
you should be using the Sun Studio tools if you can. But it
isn't always possible (particularly with c++) so it's not a
hard requirement. And as above, you don't have to use the wrapper
scripts at all, and nobody seems to in sfw (from my grep of the
build logs).
Mike
