source: trunk/third/gmake/README @ 15972

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