As is the case with all of the components in the SFW gate, You should be
using CC(64) (and CCC(64)) from the upper level Makefiles for your
compiler selection. You should also be using CFLAGS and LDFLAGS from
the upper level Makefiles and carefully consider it before you decide to
amend or override them. This will allow you to select the correct
compiler from the CBE and allow us to make uniform compiler changes with
the least amount of effort when the time comes (and it's coming
relatively soon).
(cd $(VER) ; env CC="$(CC)" CXX=$(CCC) ... ./configure ...)
(cd $(VER) ; env CC="$(CC)" CXX=$(CCC) ... make ...)
The SEGV situation you describe below sounds like a bug that needs to be
filed and fixed.
-Norm
Prashant Srinivasan wrote:
> Hi all, how does one set Sun Studiko Express as the preferred build
> compiler for a component(Ruby, in this case)?
>
> Ruby does some runtime compiling of C/C++ code. Compiler version
> mismatches between Ruby build time and runtime create SEGVs in certain
> points that we'd like to avoid.
>
> I believe $CC is still Sun Studio 11 in SFWNV.
>
> In browsing the /ws/onnv-tools/ subdirectory, I see SS11, SS12 but no
> Sun Studio express - so it seems impossible, but sending this out to get
> the experts opinion, and also to register a need for compiler version
> uniformity.
>
> (on a related note, I belive there is a need for compiler location
> uniformity across build time and runtime as well, programs like Ruby,
> MySQL, and ImageMagick have build directories hard coded into them that
> the integration teams have to fix).
>
