/usr/share/doc/make-doc/make.html/Overview.html is in make-doc 4.2.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- This file documents the GNU make utility, which determines
automatically which pieces of a large program need to be recompiled,
and issues the commands to recompile them.
This is Edition 0.74, last updated 21 May 2016,
of The GNU Make Manual, for GNU make version 4.2.1.
Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995,
1996, 1997, 1998, 1999, 2000, 2002, 2003, 2004, 2005, 2006, 2007,
2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 Free Software
Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with the Front-Cover Texts being "A GNU Manual,"
and with the Back-Cover Texts as in (a) below. A copy of the
license is included in the section entitled "GNU Free Documentation
License."
(a) The FSF's Back-Cover Text is: "You have the freedom to copy and
modify this GNU manual. Buying copies from the FSF supports it in
developing GNU and promoting software freedom." -->
<!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Overview (GNU make)</title>
<meta name="description" content="Overview (GNU make)">
<meta name="keywords" content="Overview (GNU make)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<link href="index.html#Top" rel="start" title="Top">
<link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html#Top" rel="up" title="Top">
<link href="Introduction.html#Introduction" rel="next" title="Introduction">
<link href="index.html#Top" rel="prev" title="Top">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="Overview"></a>
<div class="header">
<p>
Next: <a href="Introduction.html#Introduction" accesskey="n" rel="next">Introduction</a>, Previous: <a href="index.html#Top" accesskey="p" rel="prev">Top</a>, Up: <a href="index.html#Top" accesskey="u" rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Overview-of-make"></a>
<h2 class="chapter">1 Overview of <code>make</code></h2>
<p>The <code>make</code> utility automatically determines which pieces of a large
program need to be recompiled, and issues commands to recompile them.
This manual describes GNU <code>make</code>, which was implemented by Richard
Stallman and Roland McGrath. Development since Version 3.76 has been
handled by Paul D. Smith.
</p>
<p>GNU <code>make</code> conforms to section 6.2 of <cite>IEEE Standard
1003.2-1992</cite> (POSIX.2).
<a name="index-POSIX"></a>
<a name="index-IEEE-Standard-1003_002e2"></a>
<a name="index-standards-conformance"></a>
</p>
<p>Our examples show C programs, since they are most common, but you can use
<code>make</code> with any programming language whose compiler can be run with a
shell command. Indeed, <code>make</code> is not limited to programs. You can
use it to describe any task where some files must be updated automatically
from others whenever the others change.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a href="#Preparing" accesskey="1">Preparing</a>:</td><td> </td><td align="left" valign="top">Preparing and running <code>make</code>.
</td></tr>
<tr><td align="left" valign="top">• <a href="#Reading" accesskey="2">Reading</a>:</td><td> </td><td align="left" valign="top">On reading this text.
</td></tr>
<tr><td align="left" valign="top">• <a href="#Bugs" accesskey="3">Bugs</a>:</td><td> </td><td align="left" valign="top">Problems and bugs.
</td></tr>
</table>
<hr>
<a name="Preparing"></a>
<div class="header">
<p>
Next: <a href="#Reading" accesskey="n" rel="next">Reading</a>, Previous: <a href="#Overview" accesskey="p" rel="prev">Overview</a>, Up: <a href="#Overview" accesskey="u" rel="up">Overview</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<h4 class="node-heading">Preparing</h4>
<a name="Preparing-and-Running-Make"></a>
<h3 class="heading">Preparing and Running Make</h3>
<p>To prepare to use <code>make</code>, you must write a file called
the <em>makefile</em> that describes the relationships among files
in your program and provides commands for updating each file.
In a program, typically, the executable file is updated from object
files, which are in turn made by compiling source files.
</p>
<p>Once a suitable makefile exists, each time you change some source files,
this simple shell command:
</p>
<div class="example">
<pre class="example">make
</pre></div>
<p>suffices to perform all necessary recompilations. The <code>make</code> program
uses the makefile data base and the last-modification times of the files to
decide which of the files need to be updated. For each of those files, it
issues the recipes recorded in the data base.
</p>
<p>You can provide command line arguments to <code>make</code> to control which
files should be recompiled, or how. See <a href="Running.html#Running">How to Run
<code>make</code></a>.
</p>
<hr>
<a name="Reading"></a>
<div class="header">
<p>
Next: <a href="#Bugs" accesskey="n" rel="next">Bugs</a>, Previous: <a href="#Preparing" accesskey="p" rel="prev">Preparing</a>, Up: <a href="#Overview" accesskey="u" rel="up">Overview</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="How-to-Read-This-Manual"></a>
<h3 class="section">1.1 How to Read This Manual</h3>
<p>If you are new to <code>make</code>, or are looking for a general
introduction, read the first few sections of each chapter, skipping the
later sections. In each chapter, the first few sections contain
introductory or general information and the later sections contain
specialized or technical information.
The exception is the second chapter, <a href="Introduction.html#Introduction">An
Introduction to Makefiles</a>, all of which is introductory.
</p>
<p>If you are familiar with other <code>make</code> programs, see <a href="Features.html#Features">Features of GNU <code>make</code></a>, which lists the enhancements GNU
<code>make</code> has, and <a href="Missing.html#Missing">Incompatibilities and Missing
Features</a>, which explains the few things GNU <code>make</code> lacks that
others have.
</p>
<p>For a quick summary, see <a href="Running.html#Options-Summary">Options Summary</a>, <a href="Quick-Reference.html#Quick-Reference">Quick Reference</a>,
and <a href="Rules.html#Special-Targets">Special Targets</a>.
</p>
<hr>
<a name="Bugs"></a>
<div class="header">
<p>
Previous: <a href="#Reading" accesskey="p" rel="prev">Reading</a>, Up: <a href="#Overview" accesskey="u" rel="up">Overview</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Problems-and-Bugs"></a>
<h3 class="section">1.2 Problems and Bugs</h3>
<a name="index-reporting-bugs"></a>
<a name="index-bugs_002c-reporting"></a>
<a name="index-problems-and-bugs_002c-reporting"></a>
<p>If you have problems with GNU <code>make</code> or think you’ve found a bug,
please report it to the developers; we cannot promise to do anything but
we might well want to fix it.
</p>
<p>Before reporting a bug, make sure you’ve actually found a real bug.
Carefully reread the documentation and see if it really says you can do
what you’re trying to do. If it’s not clear whether you should be able
to do something or not, report that too; it’s a bug in the
documentation!
</p>
<p>Before reporting a bug or trying to fix it yourself, try to isolate it
to the smallest possible makefile that reproduces the problem. Then
send us the makefile and the exact results <code>make</code> gave you,
including any error or warning messages. Please don’t paraphrase
these messages: it’s best to cut and paste them into your report.
When generating this small makefile, be sure to not use any non-free
or unusual tools in your recipes: you can almost always emulate what
such a tool would do with simple shell commands. Finally, be sure to
explain what you expected to occur; this will help us decide whether
the problem was really in the documentation.
</p>
<p>Once you have a precise problem you can report it in one of two ways.
Either send electronic mail to:
</p>
<div class="example">
<pre class="example"> bug-make@gnu.org
</pre></div>
<p>or use our Web-based project management tool, at:
</p>
<div class="example">
<pre class="example"> http://savannah.gnu.org/projects/make/
</pre></div>
<p>In addition to the information above, please be careful to include the
version number of <code>make</code> you are using. You can get this
information with the command ‘<samp>make --version</samp>’. Be sure also to
include the type of machine and operating system you are using. One
way to obtain this information is by looking at the final lines of
output from the command ‘<samp>make --help</samp>’.
</p>
<hr>
<div class="header">
<p>
Previous: <a href="#Reading" accesskey="p" rel="prev">Reading</a>, Up: <a href="#Overview" accesskey="u" rel="up">Overview</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|