Version 13 (modified by bird, 16 years ago) (diff)


Solaris build instructions

The Solaris port of VirtualBox is work in progress and so is this page. The current page is just an edited version of the GNU/Linux one.


You need:

  • Solaris Nevada build 70 and Solaris Developer Express 07/09 are the oldest versions VirtualBox can be expected to build on. Build 75 or later is strongly recommended.
  • GCC 3.4.3. It will probably work with 3.4.6 or even 4.x.y, but 3.4.3 is the one we've tried and which problems we have work around.
  • as86. This ships with the Solaris builds we're using.
  • bcc (Bruce Evans C Compiler). This ships with the Solaris builds we're using.
  • IASL (Intel ACPI compiler). Checked into the source tree.
  • xsltproc (libxslt, XML style sheet processor). Ships with the Solaris builds we're using.
  • libxerces (Xerces XML parser; the C++, not the Java version). You'll probably have to build this yourself or see below.
  • libxalan (Xalan XSL library, depends on Xerces; again, the C++, not the Java version). You'll probably have to build this yourself or see below.
  • Qt 3.3.x (with x >= 5 if possible). You'll have to build this yourself.
    Make sure QTDIR is defined and that the libraries are in the LD_LIBRARY_PATH environment variable.
    The sources:
    Configure example (the -I arguments are for working around headers in odd locations):
    ./configure -v -platform solaris-g++-64 -thread -shared -stl -largefile -tablet -sm -disable-sql \
        -qt-imgfmt-jpeg -qt-imgfmt-png -qt-imgfmt-mng -qt-libjpeg -qt-libpng -qt-libmng -qt-zlib \
        -prefix /opt/vboxose-qt \
        -I/usr/include \
        -I/usr/X11/include \
        -I/usr/X11/share/include \
  • libIDL. This ships with the Solaris builds we're using.
  • The PATH and LD_LIBRARY_PATH has to include the following directories (replace bin with lib for the LD_LIBRARY_PATH):
    • /usr/sfw/bin - for gcc and related tools.
    • /usr/ccs/bin - for ar and other tools.
    • $QTDIR/bin - for Qt.

The xerces and xalan sources we use together with the appropriate kBuild makefiles can be found here: Untar them into the VirtualBox trunk directory. Add --build-xalan as argument to configure if using these sources.

Building VirtualBox

  1. Change to the root directory of the sources and execute the configure script: ./configure. If it finds everything it needs, it will create a file called 'AutoConfig.kmk' containing paths to the various tools on your system. Also, it will create an environment setup script called This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten).
  1. Whenever you want to build VirtualBox, you have to open a shell and source the generated environment setup script '', i.e. do
    source ./
  1. To build a release package, type kmk all. This produces the required binaries in out/solaris.x86/release/bin/. (If you want to build a debug version, type kmk BUILD_TYPE=debug.) In case you have more than one CPU core, you could take advantage of our parallel build system by supplying -j3 (number of cores + 1) as an option to kmk.

Running your build

You can run VirtualBox directly from the build target directory (out/solaris.x86/release/bin/). But first of all, you must build and install the VirtualBox kernel module. There is a script src/VBox/HostDrivers/Support/solaris/ which does this for you. It requires you to either install sudo or run it as root.

Next you should start the VirtualBox XPCOM daemon using

cd ./out/solaris.x86/release/bin

Finally, you can start one of the frontends, e.g.


Note that the LD_LIBRARY_PATH=".:$LD_LIBRARY_PATH" is required because we have to find our .so files and the output directory is not in the system's library path.
ContactPrivacy policyTerms of Use