VirtualBox

source: kBuild/vendor/gnumake/2005-05-16/README.cvs

Last change on this file was 280, checked in by bird, 20 years ago

Current make snaphot, 2005-05-16.

  • Property svn:eol-style set to native
File size: 3.2 KB
Line 
1 -*-text-*-
2
3Obtaining CVS Code
4------------------
5
6This seems redundant, since if you're reading this you most likely have
7already performed this step; however, for completeness, you can obtain
8the GNU make source code via anonymous CVS from the FSF's Savannah
9project <http://savannah.gnu.org/projects/make/>:
10
11 $ cvs -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/make co make
12
13You might want to use the "-z3" option to get compression, and you most
14certainly will want the -P option to avoid unneeded directories
15cluttering up your source. Personally I add these (as well as -dP for
16update) to my ~/.cvsrc file.
17
18
19If you have an older version of CVS, you might have to login first.
20There is no password; just hit the ENTER key if you are asked for one.
21
22
23Building From CVS
24-----------------
25
26To build GNU make from CVS, you will need Autoconf, Automake, and
27Gettext, and any tools that those utilities require (GNU m4, Perl,
28etc.). See the configure.in file to find the minimum versions of each
29of these tools. You will also need a copy of wget.
30
31After checking out the code, you will need to perform these steps to get
32to the point where you can run "make".
33
34
35 1) $ autoreconf -i -s
36
37 This rebuilds all the things that need rebuilding, installing
38 missing files as symbolic links.
39
40 You may get warnings here about missing files like README, etc.
41 Ignore them, they are harmless.
42
43
44 2) $ ./configure
45
46 Generate a Makefile
47
48
49 3) $ make update
50
51 Use wget to retrieve various other files that GNU make relies on,
52 but does not keep in its own source tree.
53
54 NB: You may need GNU make to correctly perform this step; if you use
55 a platform-local make you may get problems with missing files in doc/.
56
57
58At this point you have successfully brought your CVS copy of the GNU
59make source directory up to the point where it can be treated
60more-or-less like the official package you would get from ftp.gnu.org.
61That is, you can just run:
62
63 $ make && make check && make install
64
65to build and install GNU make.
66
67
68Creating a Package
69------------------
70
71Once you have performed the above steps (including the configuration and
72build) you can create a GNU make package. This is very simple, just
73run:
74
75 $ make dist-gzip
76
77and, if you like:
78
79 $ make dist-bzip2
80
81Even better, you should run this:
82
83 $ make distcheck
84
85Which will build both .gz and .bz2 package files, then unpack them into
86a temporary location, try to build them, and repack them, verifying that
87everything works, you get the same results, _and_ no extraneous files
88are left over after the "distclean" rule--whew!! Now, _that_ is why
89converting to Automake is worth the trouble! A big "huzzah!" to Tom
90T. and the AutoToolers!
91
92
93That's it, you're done!
94
95
96Appendix A - For The Brave
97--------------------------
98
99For those of you who trust me implicitly, or are just brave (or
100foolhardy), here is a canned sequence of commands to build a GNU make
101distribution package from a virgin CVS source checkout (assuming all the
102prerequisites are available of course).
103
104This list is eminently suitable for a quick swipe o' the mouse and a
105swift click o' mouse-2 into an xterm. Go for it!
106
107
108autoreconf -i -s
109./configure
110make update
111make
112make check
113make distcheck
Note: See TracBrowser for help on using the repository browser.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette