3 This code is intended for use with Linux 2.2.xx, 2.4.xx,
4 2.6.xx, and hopefully all future kernels. You should be
5 running a system with libc 6, but libc 5 might work too.
12 Only the second ("make install") is needed if you just
13 want to build and install procps in the normal way.
15 If you wish to test before installing, use the scripts
16 named t, v, and p to ensure that the correct libproc
17 (the new one) is used during your testing.
19 You may set SKIP to avoid building or installing things.
22 make SKIP='/bin/kill /usr/share/man/man1/kill.1' install
24 Use SHARED=0 to build procps without shared libraries.
25 This may be useful for installing in your home directory.
27 make SHARED=0 DESTDIR=$HOME install
29 Suppose you wanted to install stuff in strange places.
30 You might do something like this:
32 make usr/bin=/tmp/Q/i/ DESTDIR=/tmp/Q install="install -D" ldconfig=echo install
34 If cross-compiling, you might need to set lib64 to
35 either "lib" or "lib64". You might need to set m64 to
36 -m64, -m32, or nothing at all. Some examples:
38 make lib64=lib m64=-m32 # for a bi-arch gcc
39 make lib64=lib64 CC=x86_64-gcc
40 make lib64=lib CC=alpha-gcc
44 If you are a downstream maintainer (packager) for a Linux distribution,
45 please avoid causing troubles. This section applies to you.
47 Send patches in regularly. Many patches made by vendors have been buggy,
48 some quite severely so. Sending in a patch will at least get it reviewed,
49 if not included. There is a procps test suite that must be passed.
50 Forward all bug reports. If your bug database is public and busy enough
51 to bother with, please make this known. Follow Debian's lead in making
52 the bug database easy to comment on via email w/o need for an account.
54 Do not change the user interface. Many of the programs are intended to be
55 compatible with Solaris, FreeBSD, AIX, IRIX, Tru64, and the UNIX standard.
56 Your nice new command options WILL BE BROKEN as needed to ensure that
57 procps remains compatible with the rest of the world. Sysadmins hate to
58 deal with incompatible behavior. If you need a new option, ask for it.
60 For normal packages, ensure that you do not add debugging flags
61 to the CFLAGS variable. If debugging flags are present, the Makefile
62 will avoid adding several optimizations that would interfere with gdb.
64 There should be no need to modify the Makefile. You can set variables
65 on the "make" command line or use "make -e" to pass variables from
70 Debian users should use the Debian bug tracking system.
71 Email to albert@users.sf.net or csmall@debian.org or
72 procps-feedback@lists.sf.net will also work.