These instructions cover the older “Nevada” gate used during OpenSolaris and Solaris 11 development, and are left as historical reference for anyone still building that gate for a distro based on the OpenSolaris sources. See Build Instructions for the instructions for building the current Solaris X11 sources.
To get the X gate, clone the Mercurial repostory by running:
After cloning the X gate repository, you will need to download the original open source packages they modify.
The sources include a script named download-tarballs that you can run to do this. It assumes running
/usr/bin/wget can connect to Internet websites. If you need to set it to use web proxies, run "
man wget" for instructions.
To download all needed sources:
To delete all current tarballs and re-download all needed sources:
(c for “clobber”)
To see what it will do without connecting to any sites:
To build 64-bit software, you will need to be running in 64-bit mode (which on x86 requires an AMD64 or Intel EM64T capable CPU).
Starting with X build 144, the X consolidation generates packages in IPS format instead of SVR4. This requires at least build 142 of the IPS software be installed in order to build the packages.
To build the software, simply cd into the top level directory and run
To build the software and create packages, add the -p flag to buildit:
Output of various stages is stored into log files which you can check for errors with the included
|build||file under |
The built binaries are found after the build in a proto area:
Builds before 144:
Builds 144 and later:
The built packages will be found in the directory:
To install the packages from
proto-packages/installdir, run the included
The built packages will be found in a repository in the directory
proto/pkg_i386 as appropriate.
Builds made by individual developers default to using the publisher name
xnv-devel but that can be overridden via flags to the
make_release_packages scripts. They will depend on the versions of packages from other consolidations that were installed on the system they built them on.
The recommended mechanism for installing any of these builds is the
onu tool provided by ON. You can install the
pkg:/developer/build/onbld package from build 136 or later of ON to get a local copy installed as
onu will create a new boot environment and install the packages there - you will then need to reboot into that BE to use them. Since none of the X packages have the reboot required flag, it is possible to use
pkg to directly install them to the live BE, but then you have more work to do if you need to switch back to the previous versions.
Note that onu uses
pkg image-update , which means there are two important things to remember:
pkg -R /tmp/onu.* install package-name. To install all the packages provided by the X consolidation for the build in your BE, you can install the group package
Example: Install to a new BE named "X144" that is cloned from the current BE:
# onu -O -u file://`pwd`/proto/pkgs_i386 -U xnv-devel -t X144