diff options
-rw-r--r-- | Mach/BuildingOskitMach.mdwn | 72 |
1 files changed, 38 insertions, 34 deletions
diff --git a/Mach/BuildingOskitMach.mdwn b/Mach/BuildingOskitMach.mdwn index bc033a9b..edd1eaff 100644 --- a/Mach/BuildingOskitMach.mdwn +++ b/Mach/BuildingOskitMach.mdwn @@ -26,28 +26,29 @@ First you need to checkout the relevant sources. The recommended document for accessing the Hurd CVS on Savannah is at <http://savannah.gnu.org/cvs/?group=hurd> -This is only a brief restatement, which may be inaccurate. Setup your environment with the CVSROOT variable. How you do this may differ between shells. +This is only a brief restatement, which may be inaccurate. Setup your environment with the `CVSROOT` variable and login as anonymous. How you do this may differ between shells. - CVSROOT=":pserver:anoncvs@anoncvs.gnu.org:/cvsroot/hurd" + $ export CVSROOT=":pserver:anoncvs@anoncvs.gnu.org:/cvsroot/hurd" + $ cvs login # Press Enter when asking for password **_Gnu Mach:_** -All development, apart from critical bug fixes, is done on the upcoming 2.0 release. Previously the oskit-branch of gnumach, now on HEAD (the default CVS tag). +All development, apart from critical bug fixes, is done on the upcoming 2.0 release. Previously the `oskit-branch` of gnumach, now on `HEAD` (the default CVS tag). - cvs -z3 co gnumach + $ cvs -z3 co gnumach -In case you have been tracking the oskit-branch and want to move to the current HEAD branch you can issue the following instead to update your tree. +In case you have been tracking the oskit-branch and want to move to the current `HEAD` branch you can issue the following instead to update your tree. - cd <YOUR MACH DIR> - cvs -z3 update -r HEAD -Pd + $ cd <YOUR MACH DIR> + $ cvs -z3 update -r HEAD -Pd -Where <YOUR MACH DIR> can be gnumach, oskit-mach, or similar. +Where <YOUR MACH DIR> can be `gnumach`, `oskit-mach`, or similar. **_The Hurd servers:_** In case you want to build the Hurd servers as well, you can check them out with: - cvs -z3 co hurd + $ cvs -z3 co hurd **_Inteface generator:_** @@ -55,7 +56,7 @@ See the [[Mig/MachInterfaceGenerator]] for more information. Check it out using - cvs -z3 co mig + $ cvs -z3 co mig ## <a name="Building"> Building </a> @@ -74,33 +75,34 @@ Do _not_ forget to apply all known [[Mach/UsefulOskitPatches]] before starting t The attached [[ATTACHURLmodulesx86pc]], or [[ATTACHURLmodules-lightx86pc]], is an example setup, your needs may vary but this one works for standard COTS PC's. Now, how to configure and build the OSKit. - # cd oskit-20020317/ - # mkdir build - # cd build - # CC=gcc-2.95 \ + $ cd oskit-20020317/ + $ mkdir build + $ cd build + $ CC=gcc-2.95 \ CFLAGS="-g" \ ../configure --prefix=/usr/local \ - --enable-debug - # make - # sudo make install + --enable-debug \ + --enable-modulefile=modules-light.x86.pc + $ make + $ sudo make install ### <a name="Mach_Interface_Generator"> Mach Interface Generator </a> To build any Mach kernel you need an interface generator, MiG. To be on the safe side, use the CVS version. If you use Debian, you can install package [mig-i386-gnu](http://packages.debian.org/mig-i386-gnu). If you don't use Debian or want to compile MiG by yourself on Linux/\*BSD system, you must first install Mach headers. In Mach directory do: - mkdir build - cd build - ../configure --prefix=/usr # Default prefix is / ! - make -k install-headers # -k is for ignoring errors + $ mkdir build + $ cd build + $ ../configure --prefix=/usr # Default prefix is / ! + $ sudo make -k install-headers # -k is for ignoring errors Now you are ready to compile and install MiG (commands are in Mig's source directory): - automake --add-missing # Make link to `depcomp' - mkdir build - cd build - ../configure - make - make install + $ automake --add-missing # sometimes it's needed + $ mkdir build + $ cd build + $ ../configure + $ make + $ sudo make install ### <a name="GNUmach_2_0_OSKit_Mach_"> </a> GNUmach 2.0 (OSKit-Mach) @@ -108,10 +110,10 @@ Different to its half sister, the OSKit-Mach kernel does _not_ need a cross comp **_Configuring:_** - # cd oskit-mach - # mkdir build - # cd build - # MIG=/usr/local/bin/mig \ + $ cd gnumach + $ mkdir build + $ cd build + $ MIG=/usr/local/bin/mig \ CC=gcc-3.2 \ CFLAGS="-g -O" \ OSKIT_LIBDIR=/usr/local/lib/oskit \ @@ -128,9 +130,9 @@ Instead of using `make kernel` to build kernel, in OSKit-Mach you have to use < Thus, to build a IDE capable kernel with 3Com Vortex Boomerang support you use the following: - # make kernel-ide+ethernet_vortex - # sudo make install - # sudo gzip -f /gnu/boot/oskit-mach + $ make kernel-ide+ethernet_vortex + $ sudo make install + $ sudo gzip -f /gnu/boot/oskit-mach If you want to use tftp to download the kernel from Grub and don't care about the symbols I recommend either stripping or removing the `--enable-debug` and `-g` statements. @@ -166,3 +168,5 @@ Updated by: -- [[Main/LuisBustamante]] - 04 Jun 2002 Moving from oskit-branch to HEAD. -- [[Main/JoachimNilsson]] - 05 Jun 2002 Add instructions on compiling MiG. -- [[Main/OgnyanKulev]] - 15 Dec 2002 + +Replaced commands' prompt # with $ and other minor changes. -- [[Main/OgnyanKulev]] - 20 Dec 2002 |