1 | This directory contains the 3.79.1 release of GNU Make. |
---|
2 | |
---|
3 | See the file NEWS for the user-visible changes from previous releases. |
---|
4 | In addition, there have been bugs fixed. |
---|
5 | |
---|
6 | Please check the system-specific notes below for any caveats related to |
---|
7 | your operating system. |
---|
8 | |
---|
9 | For general building and installation instructions, see the file INSTALL. |
---|
10 | |
---|
11 | If you need to build GNU Make and have no other `make' program to use, |
---|
12 | you can use the shell script `build.sh' instead. To do this, first run |
---|
13 | `configure' as described in INSTALL. Then, instead of typing `make' to |
---|
14 | build the program, type `sh build.sh'. This should compile the program |
---|
15 | in the current directory. Then you will have a Make program that you can |
---|
16 | use for `./make install', or whatever else. |
---|
17 | |
---|
18 | Some systems' Make programs are broken and cannot process the Makefile for |
---|
19 | GNU Make. If you get errors from your system's Make when building GNU |
---|
20 | Make, try using `build.sh' instead. |
---|
21 | |
---|
22 | |
---|
23 | GNU Make is free software. See the file COPYING for copying conditions. |
---|
24 | |
---|
25 | |
---|
26 | Documentation |
---|
27 | ------------- |
---|
28 | |
---|
29 | GNU make is fully documented in the GNU Make manual, which is contained |
---|
30 | in this distribution as the file make.texinfo. You can also find |
---|
31 | on-line and preformatted (PostScript and DVI) versions at the FSF's web |
---|
32 | site. There is information there about ordering hardcopy documentation. |
---|
33 | |
---|
34 | http://www.gnu.org/ |
---|
35 | http://www.gnu.org/doc/doc.html |
---|
36 | http://www.gnu.org/manual/manual.html |
---|
37 | |
---|
38 | You can also find the latest versions of GNU Make from there. |
---|
39 | |
---|
40 | |
---|
41 | Bug Reporting |
---|
42 | ------------- |
---|
43 | |
---|
44 | You can send GNU make bug reports to <bug-make@gnu.org>. Please see the |
---|
45 | section of the GNU make manual entitled `Problems and Bugs' for |
---|
46 | information on submitting useful and complete bug reports. |
---|
47 | |
---|
48 | You can also use the FSF's online bug tracking system to submit new |
---|
49 | problem reports or search for existing ones. A web interface is |
---|
50 | available here: |
---|
51 | |
---|
52 | http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl |
---|
53 | |
---|
54 | Use the Category "make". |
---|
55 | |
---|
56 | If you need help using GNU make, try these forums: |
---|
57 | |
---|
58 | help-make@gnu.org |
---|
59 | help-utils@gnu.org |
---|
60 | news:gnu.utils.help |
---|
61 | news:gnu.utils.bug |
---|
62 | |
---|
63 | |
---|
64 | CVS Access |
---|
65 | ---------- |
---|
66 | |
---|
67 | The GNU make source repository is available via anonymous CVS from the |
---|
68 | GNU Subversions CVS server; look here for details: |
---|
69 | |
---|
70 | http://www.gnu.org/software/devel.html |
---|
71 | |
---|
72 | Please note: you won't be able to build GNU make from CVS without |
---|
73 | installing appropriate maintainer's tools, such as automake, autoconf, |
---|
74 | GNU make, and GCC. There are no instructions on this included with the |
---|
75 | tree, so you must be familiar with the installation and use of these |
---|
76 | tools. We make no guarantees about the contents or quality of the |
---|
77 | latest code in the CVS repository: it is not unheard of for code that is |
---|
78 | known to be broken to be checked in. Use at your own risk. |
---|
79 | |
---|
80 | |
---|
81 | Ports |
---|
82 | ----- |
---|
83 | |
---|
84 | - See README.customs for details on integrating GNU make with the |
---|
85 | Customs distributed build environment from the Pmake distribution. |
---|
86 | |
---|
87 | - See readme.vms for details about GNU Make on OpenVMS. |
---|
88 | |
---|
89 | - See README.Amiga for details about GNU Make on AmigaDOS. |
---|
90 | |
---|
91 | - See README.W32 for details about GNU Make on Windows NT, 95, or 98. |
---|
92 | |
---|
93 | - See README.DOS for compilation instructions on MS-DOS and MS-Windows |
---|
94 | using DJGPP tools. |
---|
95 | |
---|
96 | A precompiled binary of the MSDOS port of GNU Make is available as part |
---|
97 | of DJGPP; see the WWW page http://www.delorie.com/djgpp/ for more |
---|
98 | information. |
---|
99 | |
---|
100 | Please note there are two _separate_ ports of GNU make for Microsoft |
---|
101 | systems: a native Windows tool built with (for example) MSVC or Cygwin, |
---|
102 | and a DOS-based tool built with DJGPP. Please be sure you are looking |
---|
103 | at the right README! |
---|
104 | |
---|
105 | |
---|
106 | System-specific Notes |
---|
107 | --------------------- |
---|
108 | |
---|
109 | It has been reported that the XLC 1.2 compiler on AIX 3.2 is buggy such |
---|
110 | that if you compile make with `cc -O' on AIX 3.2, it will not work correctly. |
---|
111 | It is said that using `cc' without `-O' does work. |
---|
112 | |
---|
113 | One area that is often a problem in configuration and porting is the code |
---|
114 | to check the system's current load average. To make it easier to test and |
---|
115 | debug this code, you can do `make check-loadavg' to see if it works |
---|
116 | properly on your system. (You must run `configure' beforehand, but you |
---|
117 | need not build Make itself to run this test.) |
---|
118 | |
---|
119 | Another potential source of porting problems is the support for large |
---|
120 | files (LFS) in configure for those operating systems that provide it. |
---|
121 | Please report any bugs that you find in this area. If you run into |
---|
122 | difficulties, then as a workaround you should be able to disable LFS by |
---|
123 | adding the `--disable-largefile' option to the `configure' script. |
---|
124 | |
---|
125 | On systems that support micro- and nano-second timestamp values and |
---|
126 | where stat(2) provides this information, GNU make will use it when |
---|
127 | comparing timestamps to get the most accurate possible result. However, |
---|
128 | at the moment there is no system call (that I'm aware of) that will |
---|
129 | allow you to *set* a timestamp to a micro- or nano-second granularity. |
---|
130 | This means that "cp -p" and other similar tools (tar, etc.) cannot |
---|
131 | exactly duplicate timestamps with micro- and nano-second granularity. |
---|
132 | If your build system contains rules that depend on proper behavior of |
---|
133 | tools like "cp -p", you should configure make to not use micro- and |
---|
134 | nano-second timestamps with the --disable-nsec-timestamps flag. |
---|