版本 39 和 Solaris build instructions 的 版本 40 之間的變動

時間撮記:

2011-5-26 上午10:10:57 (13 年 前)

作者:

Ramshankar Venkataraman

註解:

--

Solaris build instructions

@@ -62 +62 @@
 == Building !VirtualBox ==
 
- 1. Change to the root directory of the sources and execute the configure script: `./configure --disable-hardening`. 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 `env.sh`.  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. Change to the VirtualBox root directory of the sources and execute the configure script:
+{{{
+`./configure --disable-hardening`
+}}}
+
+ 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 `env.sh`.  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).
 
  2. Whenever you want to build !VirtualBox, you have to open a shell and source the generated environment setup script 'env.sh', i.e. do
@@ -69 +74 @@
 }}}
 
- 3. 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`.)
+ 3. 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
+}}}
 
+4. If you made a hardened build (that is, you omitted the --disable-hardened switch from configure) you have to set some symbolic links manually to be able to start VMs from the bin/ directory:
+
+{{{
+cd out/solaris.amd64/release/bin/components
+ln -s ../VBoxDDU.so .
+ln -s ../VBoxREM.so .
+ln -s ../VBoxRT.so .
+ln -s ../VBoxVMM.so .
+ln -s ../VBoxXPCOM.so .
+}}}
 
 == Running your build ==
@@ -95 +117 @@
 The config script only (re)loads drivers that are found in the appropriate locations (don't forget to copy the ".conf" files).
 
+If you made a ''hardened build'', make sure that the setuid stubs have the correct permissions:
+{{{
+for f in VirtualBox VBoxHeadless VBoxSDL VBoxBFE VBoxNetDHCP VBoxNetAdpCtl; do
+  chown root.root $f
+  chmod 4511 $f
+done
+}}}
+
+
 Finally, you can start one of the frontends, e.g.
 {{{