diff options
| -rw-r--r-- | Mach/BuildingOskitMach.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Mach/BuildingOskitMach.mdwn b/Mach/BuildingOskitMach.mdwn index 297c3d0c..43a5261a 100644 --- a/Mach/BuildingOskitMach.mdwn +++ b/Mach/BuildingOskitMach.mdwn @@ -33,7 +33,7 @@ This is only a brief restatement, which may be inaccurate. Setup your environmen **_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 (OSKit/Mach). A potentially confusing point is that the code for OSKit/Mach (as opposed to the 1.X release, aka "GNU Mach") is now on the `TRUNK` of the 'gnumach' CVS module. In the past the trunk was 1.X (GNU Mach) and 2.0 (OSKit/Mach) was a branch. $ cvs -z3 co gnumach @@ -108,7 +108,7 @@ Now you are ready to compile and install MiG (commands are in Mig's source direc ### <a name="GNUmach_2_0_OSKit_Mach_"> </a> GNUmach 2.0 (OSKit-Mach) -Different to its half sister, the OSKit-Mach kernel does _not_ need a cross compiler. The regular gcc for your x86 Linux system does just fine. However, you might want to use gcc 3.2 with the latest and greatest CVS version of Mach. +Unlike its half sister, the OSKit-Mach kernel does _not_ need a cross compiler. The regular gcc for your x86 Linux system does just fine. However, you might want to use gcc 3.2 with the latest and greatest CVS version of Mach. **_Configuring:_** |