6 This seems redundant, since if you're reading this you most likely have
7 already performed this step; however, for completeness, you can obtain
8 the GNU make source code via anonymous CVS from the FSF's Savannah
9 project <http://savannah.gnu.org/projects/make/>:
11 $ cvs -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/make co make
13 You might want to use the "-z3" option to get compression, and you most
14 certainly will want the -P option to avoid unneeded directories
15 cluttering up your source. Personally I add these (as well as -dP for
16 update) to my ~/.cvsrc file.
19 If you have an older version of CVS, you might have to login first.
20 There is no password; just hit the ENTER key if you are asked for one.
26 To build GNU make from CVS, you will need Autoconf 2.53 (or better),
27 Automake 1.6.1 (or better), and Gettext 0.11.3-pre2 (or better), and any
28 tools that those utilities require (GNU m4, Perl, etc.).
30 After checking out the code, you will need to perform these steps to get
31 to the point where you can run "configure" then "make".
33 Hopefully at some point in the (near) future this will all be obsolete
34 and you can just run "autoreconf" and have it DTRT.
39 This will instantiate various m4 macros files, etc. in the config
43 2) $ aclocal -I config
45 Generate the proper aclocal.m4 file.
50 Generate a "config.h.in" file from the contents of configure.in,
54 4) $ automake --add-missing
56 Add (symlink) missing files into the distribution, and generate
57 Makefile.in's from Makefile.am's.
59 You will see these perhaps unexpected messages (among others which
60 you should be expecting :)); just ignore them--I know what I'm doing
63 Makefile.am: required file `./README' not found
64 configure.in:xxx: required file `./build.sh.in' not found
65 Makefile.am:xxx: automatically discovered file `getloadavg.c' should not be explicitly mentioned
70 Generate a "configure" script from configure.in and acinclude.m4.
73 At this point you have successfully brought your CVS copy of the GNU
74 make source directory up to the point where it can be treated
75 more-or-less like the official package you would get from ftp.gnu.org.
76 That is, you can just run:
78 $ ./configure && make && make check && make install
80 to build and install GNU make.
86 Once you have performed the above steps (including the configuration and
87 build) you can create a GNU make package. This is very simple, just
96 Even better, you should run this:
100 Which will build both .gz and .bz2 package files, then unpack them into
101 a temporary location, try to build them, and repack them, verifying that
102 everything works, you get the same results, _and_ no extraneous files
103 are left over after the "distclean" rule--whew!! Now, _that_ is why
104 converting to Automake is worth the trouble! A big "huzzah!" to Tom
105 T. and the AutoToolers!
108 That's it, you're done!
111 Appendix A - For The Brave
112 --------------------------
114 For those of you who trust me implicitly, or are just brave (or
115 foolhardy), here is a canned sequence of commands to build a GNU make
116 distribution package from a virgin CVS source checkout (assuming all the
117 prerequisites are available of course).
119 This list is eminently suitable for a quick swipe o' the old mouse and a
120 swift click o' mouse-2 into an xterm. I even grudgingly removed my use
121 of "advanced shell features" like {}. Go for it!
127 automake --add-missing