summaryrefslogtreecommitdiff
path: root/Mach
diff options
context:
space:
mode:
authorJoachim Nilsson <joachim@gnufans.org>2002-09-02 10:34:07 +0000
committerJoachim Nilsson <joachim@gnufans.org>2002-09-02 10:34:07 +0000
commitfe44bf71685bb5175586fd558f8f546d8d060f27 (patch)
tree419e8d27626cd68f4fe05f044297958ce10cdb92 /Mach
parentfe59c438bd9eb3b0b9d85928665b7d4308687695 (diff)
none
Diffstat (limited to 'Mach')
-rw-r--r--Mach/BuildingOskitMach.mdwn22
1 files changed, 16 insertions, 6 deletions
diff --git a/Mach/BuildingOskitMach.mdwn b/Mach/BuildingOskitMach.mdwn
index 0fc5e851..dedc8c1f 100644
--- a/Mach/BuildingOskitMach.mdwn
+++ b/Mach/BuildingOskitMach.mdwn
@@ -4,6 +4,8 @@
This is a brief Building OSKit Mach HowTO. It covers everything from getting the latest sources of both the [OSKit](http://www.cs.utah.edu/flux/oskit/) and the OSKit branch of the GNUmach kernel. There is also [another guide](http://www.etherhogz.org/doc/oskit-mach.html). Down to building and debugging them. On May 27 after the [[GnuMach]] 1.3 release, Roland McGrath merged OSKit Mach in the [[GnuMach]] 2.x mainline.
+To be able to actually make use of your recently checked out CVS version of the GNUMach kernel &amp; C:o you need a GNU system of [gnu-20020816.tar.gz](ftp://ftp.funet.fi/pub/gnu/alpha/gnu/hurd/contrib/marcus/gnu-20020816.tar.gz) or later.
+
## <a name="Getting_your_hands_on_the_source"> Getting your hands on the source </a>
First you need to checkout the relevant sources.
@@ -34,14 +36,15 @@ This is only a brief restatement, which may ormay not be accurate. Setup your en
All development, apart from critical bug fixes, is done on the upcoming 2.0 release. Previously the oskit-branch of gnumach.
- cvs -z3 co -d gnumach
-
-_did you mean 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.
+ cd <YOUR MACH DIR>
cvs -z3 update -r HEAD -Pd
+Where &lt;YOUR MACH DIR&gt; 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 too:
@@ -60,14 +63,14 @@ Check it out using
### <a name="The_OSKit"> </a> The OSKit
-The attached [[ATTACHURLmodulesx86pc]] file is my personal setup, it works for me. Now, how to configure and build the OSKit.
+The attached [[ATTACHURLmodulesx86pc]] 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.
**_Configuring:_**
# cd oskit-20020317/
# mkdir build
# cd build
- # ../configure --prefix=/usr/local --enable-debug
+ # CFLAGS="-g" ../configure --prefix=/usr/local --enable-debug
**_Building:_**
@@ -91,10 +94,17 @@ This will install the i386-gnu-mig in /usr/bin for you.
**_Building:_**
- # make
+ # make kernel-ide+ethernet_vortex
# sudo make install
# sudo gzip /gnu/boot/oskit-mach
+Instead of using \`make kernel' to build kernel, in OSKit-Mach you have to use \`make kernel-DRIVERS', where DRIVERS is \`DRIVER+DRIVER+...+DRIVER' (a list of drivers separated by \`+'). DRIVER can be one of:
+
+* \`ide'
+* \`floppy'
+* \`ethernet\_ETHDRV' where ETHDRV is taken from 'oskit/oskit/dev/linux\_ethernet.h'.
+* \`scsi\_SCSIDRV' where SCSIDRV is taken from \`oskit/oskit/dev/linux\_scsi.h'.
+
## <a name="Debugging"> Debugging </a>
For now, see the [[RemoteDebugOskitMach]] page.