diff options
author | Thomas Schwinge <tschwinge@gnu.org> | 2007-11-13 19:18:32 +0100 |
---|---|---|
committer | Thomas Schwinge <tschwinge@gnu.org> | 2007-11-13 19:18:32 +0100 |
commit | 0f51b6c555647b2f44621e60988414dd66ce9a46 (patch) | |
tree | 84971aa84fab6ace7f1a515863d6f773f35ba0a9 /microkernel/mach | |
parent | 8473a9df851c25bd2dd0b23b9d9c698ab9481f81 (diff) |
Use proper ikiwiki syntax.
Diffstat (limited to 'microkernel/mach')
-rw-r--r-- | microkernel/mach/gnumach/building.mdwn | 61 |
1 files changed, 37 insertions, 24 deletions
diff --git a/microkernel/mach/gnumach/building.mdwn b/microkernel/mach/gnumach/building.mdwn index e7135005..27573b64 100644 --- a/microkernel/mach/gnumach/building.mdwn +++ b/microkernel/mach/gnumach/building.mdwn @@ -1,54 +1,63 @@ Additional to the following text, a further [[example]] has be posted. -# <a name="Building_GNUMach_GNU_Mach_from_S"> </a> Building [[GNUMach]] from Source +# Building [[GNUMach]] from Source -If you want to build the [[GNUMach]] kernel yourself instead of just using a pre-built binary, follow these instructions. +If you want to build the [[GNUMach]] kernel yourself instead of just using a +pre-built binary, follow these instructions. -The unpacked source tree is around 20 MiB, and the build tree (with all drivers enabled) is around 50 MiB. +The unpacked source tree is around 20 MiB, and the build tree (with all drivers +enabled) is around 50 MiB. -## <a name="Getting_the_Source_Code"> Getting the Source Code </a> +## Getting the Source Code -### <a name="Developers_s_rcs"> Developers's rcs </a> +### Developers's RCS See [here](http://www.gnu.org/software/hurd/gnumach-download.html#cvs). $ cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co -r gnumach-1-branch gnumach -(Most probably you want to get hold of the _GNU Mach 1 branch_ and not the trunk, which is also what we've done above.) +(Most probably you want to get hold of the *GNU Mach 1 branch* and not the +trunk, which is also what we've done above.) You then have to create the automatically generatable files: $ ( cd gnumach && autoreconf --install ) -### <a name="What_Debian_is_currently_using"> What Debian is currently using </a> +### What Debian is currently using See [here](http://packages.debian.net/source/unstable/gnumach). $ apt-get source gnumach -Please see the Debian [[running/debian/FAQ]] before using _apt-get source_. +Please see the Debian [[running/debian/FAQ]] before using `apt-get source`. -## <a name="Preparing_for_the_Build"> Preparing for the Build </a> +## Preparing for the Build -### <a name="_on_Debian_systems"> ... on Debian systems </a> +### ... on Debian systems -Building GNU Mach requires the _build-essential_ and _fakeroot_ packages, their dependencies and additional packages that are specified by the source gnumach package: +Building GNU Mach requires the *build-essential* and *fakeroot* packages, their +dependencies and additional packages that are specified by the source gnumach +package: # apt-get install build-essential fakeroot # apt-get build-dep gnumach -### <a name="_on_non_Debian_systems"> ... on non-Debian systems </a> +### ... on non-Debian systems -Apart from the case that you only want to install GNU Mach's header files (see below), building GNU Mach requires you to have the Mach Interface Generator installed. See [[building_MIG|mig/Building]] about how to do that, then come back here. +Apart from the case that you only want to install GNU Mach's header files (see +below), building GNU Mach requires you to have the Mach Interface Generator +installed. See [[building_MIG|mig/building]] about how to do that, then come +back here. -Additionally, building GNU Mach requires a C compiler, a standard C library and your favourite flavor of awk (gawk) and GNU make. +Additionally, building GNU Mach requires a C compiler, a standard C library and +your favourite flavor of awk (gawk) and GNU make. -## <a name="Building_and_Installing"> Building and Installing </a> +## Building and Installing -### <a name="_Debian_deb_files"> ... Debian _.deb_ files </a> +### ... Debian `.deb` files -Change into the directory with the downloaded / unpacked _gnumach_ sources, e.g. +Change into the directory with the downloaded / unpacked GNU Mach sources, e.g. $ cd gnumach-20050801 @@ -56,20 +65,23 @@ Start the build process with $ dpkg-buildpackage -us -uc -b -rfakeroot -[[GNUMach]] is now building. To use the new kernel, you must install the resulting _.deb_ package which is located one directory above the build directory and has a similar name as the build directory, e.g. +[[GNUMach]] is now building. To use the new kernel, you must install the +resulting `.deb` package which is located one directory above the build +directory and has a similar name as the build directory, e.g. # dpkg -i ../gnumach_20050801-4_hurd-i386.deb You can now reboot your computer and enjoy the new kernel. -### <a name="_TODO_"> [TODO] </a> +### [TODO] GNU Mach should be built in a separate directory: $ mkdir gnumach-build $ cd gnumach-build -Find the path to your GNU Mach sources (_[...]/gnumach-1-branch_) and configure it: +Find the path to your GNU Mach sources (`[...]/gnumach-1-branch`) and configure +it: $ [...]/gnumach-1-branch/configure [TODO] @@ -81,21 +93,22 @@ Optionally run the (tiny) test suite: $ make check -You can then install and use _gnumach.gz_. +You can then install and use `gnumach.gz`. [TODO.] -### <a name="Installing_only_the_Header_Files"> Installing only the Header Files </a> +### Installing only the Header Files GNU Mach should be built in a separate directory: $ mkdir gnumach-build $ cd gnumach-build -Find the path to your GNU Mach sources (_[...]/gnumach-1-branch_) and configure it: +Find the path to your GNU Mach sources (`[...]/gnumach-1-branch`) and configure +it: $ [...]/gnumach-1-branch/configure --prefix= -Install the header files into e.g. _~/gnu/include/_: +Install the header files into e.g. `~/gnu/include/`: $ make DESTDIR=~/gnu install-data |