1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="ch-cross-tools-introduction">
|
---|
9 | <?dbhtml filename="introduction.html"?>
|
---|
10 |
|
---|
11 | <title>Introduction</title>
|
---|
12 |
|
---|
13 | <para>This chapter shows you how to create cross platform tools.</para>
|
---|
14 |
|
---|
15 | <para>If for some reason you have to stop and come back later, remember
|
---|
16 | to use the <command>su - lfs</command> command, and it will setup the
|
---|
17 | build environment that you left.</para>
|
---|
18 |
|
---|
19 | <sect2>
|
---|
20 | <title>Common Notes</title>
|
---|
21 |
|
---|
22 | <important>
|
---|
23 | <para>Before issuing the build instructions for a package, the package
|
---|
24 | should be unpacked as user <systemitem class="username">lfs</systemitem>,
|
---|
25 | and a <command>cd</command> into the created directory should be
|
---|
26 | performed. The build instructions assume that the <command>bash</command>
|
---|
27 | shell is in use.</para>
|
---|
28 | </important>
|
---|
29 |
|
---|
30 | <para>Several of the packages are patched before compilation, but only
|
---|
31 | when the patch is needed to circumvent a problem. A patch is often needed
|
---|
32 | in both this and the next chapters, but sometimes in only one or the other.
|
---|
33 | Therefore, do not be concerned if instructions for a downloaded patch seem
|
---|
34 | to be missing. Warning messages about <emphasis>offset</emphasis> or
|
---|
35 | <emphasis>fuzz</emphasis> may also be encountered when applying a patch.
|
---|
36 | Do not worry about these warnings, as the patch was still successfully
|
---|
37 | applied.</para>
|
---|
38 |
|
---|
39 | <para>During the compilation of most packages, there will be several
|
---|
40 | warnings that scroll by on the screen. These are normal and can safely
|
---|
41 | be ignored. These warnings are as they appear—warnings about
|
---|
42 | deprecated, but not invalid, use of the C or C++ syntax. C standards
|
---|
43 | change fairly often, and some packages still use the older standard.
|
---|
44 | This is not a problem, but does prompt the warning.</para>
|
---|
45 |
|
---|
46 | <important>
|
---|
47 | <para>After installing each package, both in this and the next chapters,
|
---|
48 | delete its source and build directories, unless specifically instructed
|
---|
49 | otherwise. Deleting the sources prevents mis-configuration
|
---|
50 | when the same package is reinstalled later.</para>
|
---|
51 | </important>
|
---|
52 |
|
---|
53 | </sect2>
|
---|
54 |
|
---|
55 | </sect1>
|
---|