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
|
Description: Correct manpage spelling errors
Author: Jörg Frings-Fürst <debian@jff-webhosting.net>
Last-Update: 2016-09-11
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: trunk/scons.1
===================================================================
--- trunk.orig/scons.1
+++ trunk/scons.1
@@ -443,7 +443,7 @@ call should use or generate the results
.PP
\-\-config=auto
.RS 4
-scons will use its normal dependency mechanisms to decide if a test must be rebuilt or not\&. This saves time by not running the same configuration tests every time you invoke scons, but will overlook changes in system header files or external commands (such as compilers) if you don\*(Aqt specify those dependecies explicitly\&. This is the default behavior\&.
+scons will use its normal dependency mechanisms to decide if a test must be rebuilt or not\&. This saves time by not running the same configuration tests every time you invoke scons, but will overlook changes in system header files or external commands (such as compilers) if you don\*(Aqt specify those dependencies explicitly\&. This is the default behavior\&.
.RE
.PP
\-\-config=force
@@ -1545,7 +1545,7 @@ The tool definition (i\&.e\&. my_tool())
.PP
If no tool list is specified, then SCons will auto\-detect the installed tools using the PATH variable in the ENV construction variable and the platform name when the Environment is constructed\&. Changing the PATH variable after the Environment is constructed will not cause the tools to be redetected\&.
.PP
-One feature now present within Scons is the ability to have nested tools\&. Tools which can be located within a subdirectory in the toolpath\&. With a nested tool name the dot represents a directory seperator
+One feature now present within Scons is the ability to have nested tools\&. Tools which can be located within a subdirectory in the toolpath\&. With a nested tool name the dot represents a directory separator
.sp
.if n \{\
.RS 4
@@ -6449,7 +6449,7 @@ env\&.Substfile(\*(Aqfoo\&.in\*(Aq, SUBS
good_foo = [(\*(Aq$foobar\*(Aq, \*(Aq$foobar\*(Aq), (\*(Aq$foo\*(Aq, \*(Aq$foo\*(Aq)]
env\&.Substfile(\*(Aqfoo\&.in\*(Aq, SUBST_DICT = good_foo)
-# UNPREDICTABLE \- one substitution could be futher expanded
+# UNPREDICTABLE \- one substitution could be further expanded
bad_bar = {\*(Aq@bar@\*(Aq: \*(Aq@soap@\*(Aq, \*(Aq@soap@\*(Aq: \*(Aqlye\*(Aq}
env\&.Substfile(\*(Aqbar\&.in\*(Aq, SUBST_DICT = bad_bar)
@@ -6681,7 +6681,7 @@ file\&. Note, that the updated
POT
and
PO
-files are usually going to be committed back to the repository, so they must be updated within the source directory (and not in variant directories)\&. Additionaly, the file listing of
+files are usually going to be committed back to the repository, so they must be updated within the source directory (and not in variant directories)\&. Additionally, the file listing of
po/
directory contains
LINGUAS
@@ -7221,7 +7221,7 @@ Example:
AllowSubstExceptions()
# Also allow a string containing a zero\-division expansion
-# like \*(Aq${1 / 0}\*(Aq to evalute to \*(Aq\*(Aq\&.
+# like \*(Aq${1 / 0}\*(Aq to evaluate to \*(Aq\*(Aq\&.
AllowSubstExceptions(IndexError, NameError, ZeroDivisionError)
.fi
.if n \{\
@@ -9196,7 +9196,7 @@ Return([vars\&.\&.\&., stop=])
.RS 4
By default, this stops processing the current SConscript file and returns to the calling SConscript file the values of the variables named in the
\fIvars\fR
-string arguments\&. Multiple strings contaning variable names may be passed to
+string arguments\&. Multiple strings containing variable names may be passed to
\fBReturn\fR\&. Any strings that contain white space
.sp
The optional
@@ -10096,7 +10096,7 @@ function to create a copy of your source
\fIvariant_dir\fR
is not found but exists under
\fIsrc_dir\fR, the file or directory is copied to
-\fIvariant_dir\fR\&. Target files can be built in a different directory than the original sources by simply refering to the sources (and targets) within the variant tree\&.
+\fIvariant_dir\fR\&. Target files can be built in a different directory than the original sources by simply referring to the sources (and targets) within the variant tree\&.
.sp
\fBVariantDir\fR
@@ -11363,7 +11363,7 @@ is used to create PDF output from an XML
.PP
DOCBOOK_FOPFLAGS
.RS 4
-Additonal command\-line flags for the PDF renderer
+Additional command\-line flags for the PDF renderer
fop
or
xep\&.
@@ -11390,7 +11390,7 @@ is used to resolve XIncludes for a given
.PP
DOCBOOK_XMLLINTFLAGS
.RS 4
-Additonal command\-line flags for the external executable
+Additional command\-line flags for the external executable
xmllint\&.
.RE
.PP
@@ -11421,7 +11421,7 @@ is used to transform an XML file via a g
.PP
DOCBOOK_XSLTPROCFLAGS
.RS 4
-Additonal command\-line flags for the external executable
+Additional command\-line flags for the external executable
xsltproc
(or
saxon,
@@ -11430,7 +11430,7 @@ xalan)\&.
.PP
DOCBOOK_XSLTPROCPARAMS
.RS 4
-Additonal parameters that are not intended for the XSLT processor executable, but the XSL processing itself\&. By default, they get appended at the end of the command line for
+Additional parameters that are not intended for the XSLT processor executable, but the XSL processing itself\&. By default, they get appended at the end of the command line for
saxon
and
saxon\-xslt, respectively\&.
@@ -14081,7 +14081,7 @@ A list of installed versions of the Metr
.PP
NAME
.RS 4
-Specfies the name of the project to package\&.
+Specifies the name of the project to package\&.
.RE
.PP
no_import_lib
@@ -16414,7 +16414,7 @@ builder\&.
.PP
_XGETTEXTFROMFLAGS
.RS 4
-Internal "macro"\&. Genrates list of
+Internal "macro"\&. Generates list of
\-D<dir>
flags from the
\fB$XGETTEXTPATH\fR
@@ -18354,7 +18354,7 @@ a = Action("build < ${SOURCE\&.file} > $
The
\fBAction\fR() global function also takes an
\fBexitstatfunc\fR
-keyword argument which specifies a function that is passed the exit status (or return value) from the specified action and can return an arbitrary or modified value\&. This can be used, for example, to specify that an Action object\*(Aqs return value should be ignored under special conditions and SCons should, therefore, consider that the action always suceeds:
+keyword argument which specifies a function that is passed the exit status (or return value) from the specified action and can return an arbitrary or modified value\&. This can be used, for example, to specify that an Action object\*(Aqs return value should be ignored under special conditions and SCons should, therefore, consider that the action always succeeds:
.sp
.if n \{\
.RS 4
|
