Build Instructions at OpenSolaris.org

You are not signed in. or register.

SFW Buildable Source for OpenSolaris

This delivery of SFW buildable source for OpenSolaris consists of a single archive:

source tarball (sfw-src-b#-DATE.tar.bz2)

General Prerequisites

Building SFW is similar to building the Operating System/Networking (ON) consolidation from source. If you are not familiar with building ON from opensolaris.org, please read the build instructions and the detailed documentation before starting your build. You will also need the following shared build/install-time tools:

compiler: Sun Studio 11 with patches as delivered for ON build 48
compiler: gcc 3.4.3 with patches as delivered with Solaris Express build 22 or later, or SFW build 22 or later.
ON build tools package (SUNWonbld-DATE.PLATFORM.tar.bz2) from ON

Unlike ON, SFW does not use BFU or BFU archives. There are no closed binaries; the entire consolidation is Open Source.

You can generally build the SFW consolidation on any OpenSolaris distribution compatible with the Solaris Express release two builds older than the SFW sources. Consult your vendor's documentation for more information about compatibility with Solaris Express. For example, to build SFW sources for build 58, your distribution must be compatible with Solaris Express build 56 or later. These release notes will always contain information about new or additional build environment requirements that may arise from time to time.

SFW requires the same compilers and support tools as ON. Be sure you have installed a recent SUNWonbld package. Note that, unlike ON, SFW does not contain these build tools, so you must install them in advance rather than relying on nightly's 't' option. In general, your build tools must be no more than 2 builds old. You can obtain the latest SUNWonbld package from the ON download site. The required Studio 11 compilers can be obtained from the Tools community. You must also have the standard Solaris gcc (from Nevada build 22 or later) installed. Note that compilers other than these specific versions have not been tested and may fail to build SFW correctly.

The buildable source may contain source for high key-strength crypto. Please note that certain countries restrict the redistribution of high key-strength crypto. If you live in one of these countries, it is your responsibility to ensure that you are complying with your country's laws in this area.

Special Requirements

Use Studio 11 compilers for SFW starting with build 49. These are the same compilers used for ON starting with build 48.

Known Issues

The nmap build may fail because of bugid 6571762 (xrender.pc depends on non-existent x11.pc). When that is fixed/worked around the cairo pkgconfig files may also have such a dependency and need to be fixed (6604593 pkg-config for gtk+-2.0 still does not work on snv_73).
curl may fail to build because libidn isn't installed on the build machine (failing a configure test that may not mention libidn). This is 6607477 (curl build should pick up libidn from the proto area first) which should be fixed in 75 but may not be.
Building SFW on a machine which has the Companion installed in /opt/sfw is not recommended. The SFW build uses "configure" which may find things in /opt/sfw. A known incident is that the apache2 build found /opt/sfw/bin/gsed and the resulting SUNWapch2r package required /opt/sfw/bin/gsed. Note that this also applies to other well-known locations like /usr/local.
The package builds may fail on large ZFS file systems (6459131 and 6558284).
If you are building x86 binaries, you must use a 64-bit build machine running the 64 bit kernel (6401063).

For Further Information

General questions on the SFW consolidation should be directed to the discussion list at sfwnv dash discuss at opensolaris dot org. Please note that the mailing lists are configured to only allow posts from list subscribers or via the web forum interface. To subscribe, see the SFW Nevada project home.

Installing from Source

Once you have downloaded the SFW source, follow these steps to build it. Suppose you are using /export/sfwnv as your workspace.

If your build machine is already configured for building ON, skip ahead to step 2. Otherwise, follow the compiler and onbld installation instructions in the ON README. These are steps 2, 3, and 4 in the onnv_36 README.

Be sure that your installed copy of gcc is up to date:

    $ /usr/sfw/bin/gcc --version
    gcc (GCC) 3.4.3 (csl-sol210-3_4-20050802)

Be sure that your installed copy of cc is up to date. If you've followed the above instructions, you should see:
```
    $ /opt/SUNWspro/bin/cc -V
```
Correct output is architecture-dependent:
```
    cc: Sun C 5.8 Patch 121015-04 2007/01/10		(sparc)
    cc: Sun C 5.8 Patch 121016-05 2007/01/10		(x86)
```
NOTE: BOTH COMPILERS are REQUIRED and must be at the correct revisions!
Create an environment file to guide tools like nightly(1) and bldenv(1).

   change GATE to the name of the top-level directory (e.g.,"sfwnv")
   
change CODEMGR_WS to the top-level path (e.g.,"/export/sfwnv").
   
change STAFFER to your login.
   
Do NOT set VERSION; this will break your build!
   
The default options are recommended.  Using other options may cause
     your build to fail or contain unnecessary noise.

To build a complete set of archives, cd to /export/sfwnv, utter
```
    # /opt/onbld/bin/nightly ./sfw-opensolaris.sh &
```
and find something else to work on for a few hours. You can monitor the build's progress using ptree(1). nightly(1) will send mail to $MAILTO when it has finished.
The results mail from nightly(1) will have an overview of the build results. A copy of the mail text and a more detailed log file will be available in the workspace (/export/sfwnv/log/log.DATE). Pieces of the detailed log are also available under usr/src. For example, usr/src/install-nd-i386.out will have the log from the x86 "make install" part of the build.
By default nightly(1) will do a "clobber" build, which includes a "make clobber" and blowing away any files that earlier builds installed into $ROOT (/export/sfwnv/proto/root_PLATFORM). To bypass these steps, do an incremental build with "nightly -i ./sfw-opensolaris.sh &". Be aware that incremental builds are not performed as often as in ON and do tend to break more frequently though.
To build a specific component, first use bldenv(1) to set up various environment variables:
```
    # cd /export/sfwnv
    # bldenv ./sfw-opensolaris.sh
    [status information from bldenv]
```
Next, you must create and partially populate the proto area:
```
    # cd $SRC
    # make setup
```
Finally, cd into the directory containing the component you wish to build, and run make:
```
    # make -f Makefile.sfw install
```
Note that all sub-makefiles are called Makefile.sfw to avoid possible collisions with the component's Makefile (if the tarball method is not chosen).