The compilers needed may depend on the consolidation you are building
and the platform(s) on which you wish to build. Prior to build 19, an
x86 build of ON used both the Sun One Studio 8 and GNU compilers by
default. This is because 32-bit objects are built with cc and CC, while
gcc is used for 64-bit objects. As of build 19, Sun Studio 10 compilers
are used by default for all objects. And effective beginning in build
38, all ON builds on all platforms require both Sun Studio 10 and a
recent version of gcc (from /usr/sfw in Solaris Express). Other
consolidations may require slightly different compilers and/or compiler
patches, so always check the latest release notes.
Because compilers used to build OpenSolaris may require special patches, links to current Studio compiler binaries will always be maintained at the OpenSolaris web site. Using other versions of compilers, assemblers, linkers, make(1), or dmake(1) is not supported and may fail to build or create binaries that do not function correctly. Therefore, you must use the compilers listed in your consolidation's release notes to ensure a successful build. From time to time the required tools will be updated; notices will be posted and newer versions made available as appropriate.
The only compilers that can be used to build the mainline OpenSolaris sources are the Sun Studio 10 tools available at http://opensolaris.org/os/community/tools/sun_studio_tools/ and the GNU Compiler Collection shipped with Solaris Express build 22 and later. If you wish to use gcc as your primary compiler (that is, if you wish the archives to contain objects built with gcc), see http://opensolaris.org/os/community/tools/gcc/. Regardless of the compiler you use, you will need a set of ON-specific build tools (onbld). You can find these tools for both SPARC and x86 platforms at http://opensolaris.org/os/downloads/on/.
The Studio 10 compilers can be installed in two ways: from an installed
image, or as a complete product. The installed image is simply a
compressed tar file containing many, but not all, of the contents of the
Studio 10 product, with patches already applied and a valid license key.
The contents are sufficient to build ON; you can learn more about
exactly what's included at
http://opensolaris.org/os/community/tools/sun_studio_tools/faqs/.
The installed image will be extracted to opt/SUNWspro beneath the
directory in which you extract it; if you extract it in the root
directory as described below, which is recommended, it will install in
the same location as the full product would. Please note that there is
no way to apply additional patches to the installed image.
Suppose you have downloaded the installed image into
/var/tmp/sunstudio10-sparc.tar.bz2, and want to install it into
/opt/SUNWspro (recommended). You could install as follows:
$ su Password: # cd / # bzip2 -dc /var/tmp/sunstudio10-sparc.tar.bz2 | tar xf -
The complete product install has its own installer and a complete manual
that includes installation instructions. See
http://docs.sun.com/app/docs/doc/819-0485 for detailed installation
instructions, including how to use the graphical and text installation
methods. You will need to install the required patches before you can
build OpenSolaris components if you use the full product; normally these
are included with the product download. See
http://opensolaris.org/os/community/tools/sun_studio_tools/ for
more information on required patches. By default, the Studio 10 product
installs into /opt/SUNWspro. You should not change this unless you
have an existing installation of Sun Workshop/Forte/Studio that you need
to preserve.
Suppose you have downloaded the product into
/var/tmp/sunstudio10-x86.tar, you wish to unpack it in
/var/tmp/studio-install, and you received a license key 'ABC123'.
You could install as follows:
$ mkdir /var/tmp/studioinstall $ cd /var/tmp/studioinstall $ tar xf /var/tmp/sunstudio10-x86.tar $ su Password: # ./batch_installer -s ABC123 ... # cd patches # patchadd -M . patchlist ...
The version of gcc needed is installed by default as part of Solaris Express builds 22 and later. If using a different distribution, consult your vendor's documentation to determine whether your version of gcc is sufficient.