Hi Sunil, If you would like to build amd64 with Studio 10 patch, and assuming that you have installed Studio 10 patch, this is what you need to do either in the environment setting, or in your environment file if you are using the "nightly" script:
# export __GNUC64='#' # export SPRO_VROOT=path-to-your-studio-10-patch-compiler Sherry On Wed, Jul 06, 2005 at 08:55:17PM -0700, Sunil wrote: > Why is the default build trying to use gcc? I am following the directions > given in the dev. reference document. The only variable that affects the gcc > usage is __GNUC which I have set promptly to '#' but no go. If I set CC=cc > then it spews some cc warnings: > > --------------------- > cd usr/src/uts > dmake > > ..... > ..... > /opt/onbld/bin/genoffsets -s /opt/onbld/bin/i386/ctfstabs -r > /opt/onbld/bin/i386/ctfconvert cc -_noecho > -_gcc=-fno-eliminate-unused-debug-symbols > -_gcc=-fno-eliminate-unused-debug-types -xarch=amd64 -Ui386 -U__i386 -O > ../../intel/amd64/ml/amd64.il -D_ASM_INLINES -Xa -xspace -Wu,-xmodel=kernel > -v -xildoff -g -xc99=%none -W0,-noglobal -errtags=yes -errwarn=%all > -erroff=E_EMPTY_TRANSLATION_UNIT -erroff=E_STATEMENT_NOT_REACHED -xc99=%none > -D_KERNEL -D_SYSCALL32 -D_SYSCALL32_IMPL -D_ELF64 -Dsun -D__sun -D__SVR4 > -Di86pc -D_MACHDEP -DOPTERON_ERRATUM_88 -DOPTERON_ERRATUM_91 > -DOPTERON_ERRATUM_93 -DOPTERON_ERRATUM_95 -DOPTERON_ERRATUM_100 > -DOPTERON_ERRATUM_108 -DOPTERON_ERRATUM_109 -DOPTERON_ERRATUM_121 > -DOPTERON_ERRATUM_122 -DOPTERON_ERRATUM_123 -DC2_AUDIT -I../../i86pc > -I../../intel -Y I,../../common <../../i86pc/ml/offsets.in >obj64/assym.h > cc: Warning: option -_ passed to ld > cc: Warning: illegal option -noecho > cc: Warning: option -_ passed to ld > cc: Warning: option -= passed to ld > cc: Warning: option -- passed to ld > cc: Warning: illegal option -fno-eliminate-unused-debug-symbols > cc: Warning: option -_ passed to ld > cc: Warning: option -= passed to ld > cc: Warning: option -- passed to ld > cc: Warning: illegal option -fno-eliminate-unused-debug-types > .... > ....so on > ----------------- > but it starts to build the rest of the stuff fine. what's the right way to > use Sun Studio compiler to build the kernel? > This message posted from opensolaris.org > _______________________________________________ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org -- [EMAIL PROTECTED], Solaris Kernel Development, http://blogs.sun.com/sherrym _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
