blob: 5e9226c9c93eb616523d3cf54c454c16c2eff4b5 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
# <a name="Building_the_Hurd_from_Source"> Building the Hurd from Source </a>
## <a name="Getting_the_Source_Code"> Getting the Source Code </a>
You can chose between getting the [sources from the developers's RCS](http://www.gnu.org/software/hurd/download.html#cvs):
$ cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/hurd co hurd
$ cd hurd
... or (if you are working on a Debian system) the ones that are used for the [current Debian hurd package](http://packages.debian.net/source/unstable/hurd):
$ apt-get source hurd # Unpacks in hurd-YYYYMMDD
$ cd hurd-*
Please see [[Distrib/DebianFAQ]] before using _apt-get source_.
The unpacked source tree is around 20MiB, and the build tree (configured with `--disable-profile`) is around 100MiB.
## <a name="Building_the_Hurd"> Building the Hurd </a>
TODO: cross compiling.
Building the Hurd requires `build-essential`, `libc-dev` and `mig` packages:
# apt-get install build-essential fakeroot
# apt-get build-dep hurd
The Hurd has to be built in a separate directory:
$ mkdir build
$ cd build
$ ../configure --disable-profile
$ make
$ make install
Notice that `make install` will install the Hurd in `/`, not in `/usr/local/` or `/local/`, so your current Hurd servers will be replaced. TODO: how to install somewhere else.
By default profiling versions of all the libraries and code are generated but this is useless in most of the cases, so we disable them by specifying `--disable-profile` on =configure='s command line.
As an alternative, you can build and install the Hurd in the Debian way (from CVS snapshot):
$ cd hurd
$ dpkg-buildpackage
If you just want to build a specific server or library, you can pass its name to `make`:
$ make ext2fs
$ make libtrivfs
This will automatically build all libraries that are required to build the requested server or library.
TODO: update.
If you want to trace the RPC calls made by some process by using `rpctrace` command, you will also want some more human-readable output of this command. This is achieved by generating `hurd.msgids` file that includes the mapping between the number of the RPC call and its name:
$ cd build/hurd
$ make hurd.msgids
$ cp hurd.msgids ~
Now you can use this file in the following way:
$ rpctrace -i ~/hurd.msgids ls
-- [[Main/OgnyanKulev]] - 08 Apr 2003
|
