1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="conventions">
|
---|
9 | <?dbhtml filename="conventions.html"?>
|
---|
10 |
|
---|
11 |
|
---|
12 | <title>Conventions Used in this Book</title>
|
---|
13 |
|
---|
14 | <sect2>
|
---|
15 | <title>Typographical Conventions</title>
|
---|
16 | <para>To make things easy to follow, a number of conventions are used
|
---|
17 | throughout the book. Here are some examples:</para>
|
---|
18 |
|
---|
19 | <screen><userinput>./configure --prefix=/usr</userinput></screen>
|
---|
20 |
|
---|
21 | <blockquote>
|
---|
22 | <para>This form of text should be typed exactly as shown unless
|
---|
23 | otherwise noted in the surrounding text. It is also used to identify
|
---|
24 | references to specific commands.</para>
|
---|
25 | </blockquote>
|
---|
26 |
|
---|
27 | <screen><computeroutput>install-info: unknown option
|
---|
28 | `--dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
|
---|
29 |
|
---|
30 | <blockquote>
|
---|
31 | <para>This form of text (fixed width font) shows screen
|
---|
32 | output, probably the result of issuing a command. It is also used to
|
---|
33 | show filenames such as <filename>/boot/grub/grub.conf</filename></para>
|
---|
34 | </blockquote>
|
---|
35 |
|
---|
36 | <para><emphasis>Emphasis</emphasis></para>
|
---|
37 |
|
---|
38 | <blockquote>
|
---|
39 | <para>This form of text is used for several purposes,
|
---|
40 | but mainly to emphasize important points, or to give examples of
|
---|
41 | what to type.</para>
|
---|
42 | </blockquote>
|
---|
43 |
|
---|
44 | <para><ulink url="https://www.&lfs-domainname;/"/></para>
|
---|
45 |
|
---|
46 | <blockquote>
|
---|
47 | <para>This form of text is used for hypertext links external to
|
---|
48 | the book, such as HowTos, download locations, websites, etc.</para>
|
---|
49 | </blockquote>
|
---|
50 |
|
---|
51 | <para><xref linkend="seamonkey"/></para>
|
---|
52 |
|
---|
53 | <blockquote>
|
---|
54 | <para>This form of text is used for links internal to
|
---|
55 | the book, such as another section describing a different package.</para>
|
---|
56 | </blockquote>
|
---|
57 |
|
---|
58 | <screen><userinput>cat > $LFS/etc/group << "EOF"
|
---|
59 | <literal>root:x:0:
|
---|
60 | bin:x:1:
|
---|
61 | ......</literal>
|
---|
62 | EOF</userinput></screen>
|
---|
63 |
|
---|
64 | <blockquote>
|
---|
65 | <para>This style is mainly used when creating configuration
|
---|
66 | files. The first command (in bold) tells the system to create
|
---|
67 | the file <filename>$LFS/etc/group</filename> from whatever is typed on the
|
---|
68 | following lines, until the sequence EOF is encountered.
|
---|
69 | Therefore, this whole section is usually typed exactly as shown.
|
---|
70 | Remember, copy and paste is your friend!</para>
|
---|
71 | </blockquote>
|
---|
72 |
|
---|
73 | <para><replaceable><REPLACED TEXT></replaceable></para>
|
---|
74 |
|
---|
75 | <blockquote>
|
---|
76 | <para>This form of text is used to encapsulate text that should be
|
---|
77 | modified, and is not to be typed as shown, or copied and pasted.
|
---|
78 | The angle brackets are not part of the literal text; they are part of the
|
---|
79 | substitution.</para>
|
---|
80 | </blockquote>
|
---|
81 |
|
---|
82 | <para><systemitem class='username'>root</systemitem></para>
|
---|
83 |
|
---|
84 | <blockquote>
|
---|
85 | <para>This form of text is used to show a specific system user or group
|
---|
86 | reference in the instructions.</para>
|
---|
87 | </blockquote>
|
---|
88 |
|
---|
89 | <para> </para> <!-- add extra white space to improve readability -->
|
---|
90 | </sect2>
|
---|
91 |
|
---|
92 | <sect2>
|
---|
93 | <title>Conventions Used for Package Dependencies</title>
|
---|
94 |
|
---|
95 | <para>When new packages are created, the software's authors depend on prior work. In
|
---|
96 | order to build a package in BLFS, these dependencies must be built before
|
---|
97 | the desired package can be compiled. For each package, prerequisites are listed
|
---|
98 | in one or more separate sections: Required, Recommended, and Optional.</para>
|
---|
99 |
|
---|
100 | <bridgehead renderas="sect3">Required Dependencies</bridgehead>
|
---|
101 |
|
---|
102 | <para>These dependencies are the bare minimum needed to
|
---|
103 | build the package. Packages in LFS, and the required
|
---|
104 | dependencies of these required packages, are omitted from this list.
|
---|
105 | Always remember to check for nested dependencies.</para>
|
---|
106 |
|
---|
107 | <bridgehead renderas="sect3">Recommended Dependencies</bridgehead>
|
---|
108 |
|
---|
109 | <para>These are dependencies the BLFS editors have determined
|
---|
110 | are important to give the package reasonable capabilities. Package
|
---|
111 | installation instructions assume they are installed. If a recommended
|
---|
112 | package is not installed, the instructions may require modification, to
|
---|
113 | accommodate the missing package.</para>
|
---|
114 |
|
---|
115 | <bridgehead renderas="sect3">Optional Dependencies</bridgehead>
|
---|
116 |
|
---|
117 | <para>These are dependencies the package <emphasis>may</emphasis> use. Integration
|
---|
118 | of optional dependencies may be automatic by the package, or
|
---|
119 | additional steps not presented by BLFS may be necessary. Optional dependencies are
|
---|
120 | sometimes listed without explicit BLFS instructions. In this case you must
|
---|
121 | determine how to perform the installation yourself. </para>
|
---|
122 |
|
---|
123 | <para> </para> <!-- add extra white space to improve readability -->
|
---|
124 | </sect2>
|
---|
125 |
|
---|
126 | <sect2>
|
---|
127 | <title>Conventions Used for Kernel Configuration Options</title>
|
---|
128 |
|
---|
129 | <para>Some packages require specific kernel configuration options.
|
---|
130 | The general layout for these looks like this:</para>
|
---|
131 |
|
---|
132 | <screen><literal>Master section --->
|
---|
133 | Subsection --->
|
---|
134 | [*] Required parameter [CONFIG_REQU_PAR]
|
---|
135 | <*> Required parameter (not as module) [CONFIG_REQU_PAR_NMOD]
|
---|
136 | <*/M> Required parameter (could be a module) [CONFIG_REQU_PAR_MOD]
|
---|
137 | <*/M/ > Optional parameter [CONFIG_OPT_PAR]
|
---|
138 | [ ] Incompatible parameter [CONFIG_INCOMP_PAR]
|
---|
139 | < > Incompatible parameter (even as module) [CONFIG_INCOMP_PAR_MOD]</literal></screen>
|
---|
140 |
|
---|
141 | <para>[CONFIG_...] on the right gives the name of the option, so you can
|
---|
142 | easily check whether it is set in your <filename>.config</filename> file.
|
---|
143 | The meaning of the various entries is:
|
---|
144 |
|
---|
145 | <blockquote>
|
---|
146 | <informaltable frame='none'><tgroup cols="2">
|
---|
147 | <colspec align="left"/><colspec align="left"/><tbody>
|
---|
148 | <row>
|
---|
149 | <entry><emphasis role="bold">Master section</emphasis></entry>
|
---|
150 | <entry>top level menu item</entry>
|
---|
151 | </row>
|
---|
152 | <row>
|
---|
153 | <entry><emphasis role="bold">Subsection</emphasis></entry>
|
---|
154 | <entry>submenu item</entry>
|
---|
155 | </row>
|
---|
156 | <row>
|
---|
157 | <entry>
|
---|
158 | <emphasis role="bold">Required parameter</emphasis></entry>
|
---|
159 | <entry>
|
---|
160 | the option can either be built-in, or not selected: it must be
|
---|
161 | selected
|
---|
162 | </entry>
|
---|
163 | </row>
|
---|
164 | <row>
|
---|
165 | <entry>
|
---|
166 | <emphasis role="bold">Required parameter (not as
|
---|
167 | module)</emphasis>
|
---|
168 | </entry>
|
---|
169 | <entry>
|
---|
170 | the option can be built-in, a module, or not selected (tri-state):
|
---|
171 | it must be selected as built-in
|
---|
172 | </entry>
|
---|
173 | </row>
|
---|
174 | <row>
|
---|
175 | <entry>
|
---|
176 | <emphasis role="bold">Required parameter (could be
|
---|
177 | a module)</emphasis>
|
---|
178 | </entry>
|
---|
179 | <entry>
|
---|
180 | the option can be built-in, a module, or not selected:
|
---|
181 | it must be selected, either as built-in or as a module
|
---|
182 | </entry>
|
---|
183 | </row>
|
---|
184 | <row>
|
---|
185 | <entry>
|
---|
186 | <emphasis role="bold">Optional parameter</emphasis>
|
---|
187 | </entry>
|
---|
188 | <entry>
|
---|
189 | rarely used: the option can be built-in, a module, or not
|
---|
190 | selected: it may be set any way you wish
|
---|
191 | </entry>
|
---|
192 | </row>
|
---|
193 | <row>
|
---|
194 | <entry>
|
---|
195 | <emphasis role="bold">Incompatible parameter</emphasis>
|
---|
196 | </entry>
|
---|
197 | <entry>
|
---|
198 | the option can either be built-in or not selected: it must
|
---|
199 | <emphasis>not</emphasis> be selected
|
---|
200 | </entry>
|
---|
201 | </row>
|
---|
202 | <row>
|
---|
203 | <entry>
|
---|
204 | <emphasis role="bold">Incompatible parameter (even as module)</emphasis>
|
---|
205 | </entry>
|
---|
206 | <entry>
|
---|
207 | the option can be built-in, a module, or not selected:
|
---|
208 | it must <emphasis>not</emphasis> be selected
|
---|
209 | </entry>
|
---|
210 | </row>
|
---|
211 | </tbody></tgroup></informaltable>
|
---|
212 | </blockquote>
|
---|
213 | </para>
|
---|
214 |
|
---|
215 | <para>Note that, depending on other selections, the angle brackets
|
---|
216 | (<>) in the configuration menu may appear as braces ({}) if the option cannot be unselected,
|
---|
217 | or even as dashes (-*- or -M-), when the choice is imposed.
|
---|
218 | The help text describing the option specifies the other selections on which this
|
---|
219 | option relies, and how those other selections are set.</para>
|
---|
220 |
|
---|
221 | <para> </para> <!-- add extra white space to improve readability -->
|
---|
222 | </sect2>
|
---|
223 |
|
---|
224 | <sect2>
|
---|
225 | <title>SBU values in BLFS</title>
|
---|
226 |
|
---|
227 | <para>As in LFS, each package in BLFS has a build time listed in Standard
|
---|
228 | Build Units (SBUs). These times are relative to the time it took to build
|
---|
229 | binutils in LFS, and are intended to provide some insight into how long it
|
---|
230 | will take to build a package. Most times listed are for a single processor
|
---|
231 | or core to build the package. In some cases, large, long running builds
|
---|
232 | tested on multi-core systems have SBU times listed with comments such
|
---|
233 | as '(parallelism=4)'. These values indicate testing was done using
|
---|
234 | multiple cores. Note that while this speeds up the build on systems with
|
---|
235 | the appropriate hardware, the speedup is not linear and to some extent
|
---|
236 | depends on the individual package and the specific hardware used. </para>
|
---|
237 |
|
---|
238 | <para>For packages which use ninja (i.e., anything using meson) or rust, by
|
---|
239 | default all cores are used; similar comments will be seen on such packages
|
---|
240 | even when the build time is minimal.</para>
|
---|
241 |
|
---|
242 | <para>Where even a parallel build takes more than 15 SBU, on certain
|
---|
243 | machines the time may be considerably greater even when the build does not
|
---|
244 | use swap. In particular, different micro-architectures will build some
|
---|
245 | files at different relative speeds, and this can introduce delays when
|
---|
246 | certain make targets wait for another file to be created. Where a large
|
---|
247 | build uses a lot of C++ files, processors with Simultaneous Multi Threading
|
---|
248 | will share the Floating Point Unit and can take 45% longer than when using
|
---|
249 | four 'prime' cores (measured on an intel i7 using taskset and keeping the
|
---|
250 | other cores idle).</para>
|
---|
251 |
|
---|
252 | <para>Some packages do not support parallel builds; for these, the
|
---|
253 | make command must specify -j1. Packages that are known to impose such limits are
|
---|
254 | so marked in the text.</para>
|
---|
255 |
|
---|
256 | </sect2>
|
---|
257 |
|
---|
258 | </sect1>
|
---|