Changeset cc0e77d for part3intro/generalinstructions.xml
- Timestamp:
- 09/29/2022 09:30:17 PM (2 years ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 7978900, e18ba69
- Parents:
- eb30b32
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
part3intro/generalinstructions.xml
reb30b32 rcc0e77d 12 12 <title>General Compilation Instructions</title> 13 13 14 <para>When building packages there are several assumptions made within 15 the instructions:</para> 14 <para>Here are some things you should know about building each package:</para> 16 15 17 16 <itemizedlist> 18 17 19 18 <listitem> 20 <para>Several of thepackages are patched before compilation, but only when19 <para>Several packages are patched before compilation, but only when 21 20 the patch is needed to circumvent a problem. A patch is often needed in 22 both this and the following chapters, but sometimes in only one location. 21 both the current and the following chapters, but sometimes, when the same package 22 is built more than once, the patch is not needed right away. 23 23 Therefore, do not be concerned if instructions for a downloaded patch seem 24 24 to be missing. Warning messages about <emphasis>offset</emphasis> or 25 25 <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do 26 not worry about these warnings , asthe patch was still successfully26 not worry about these warnings; the patch was still successfully 27 27 applied.</para> 28 28 </listitem> 29 29 30 30 <listitem> 31 <para>During the compilation of most packages, there will be several32 warnings thatscroll by on the screen. These are normal and can safely be33 ignored. These warnings are as they appear—warningsabout31 <para>During the compilation of most packages, some 32 warnings will scroll by on the screen. These are normal and can safely be 33 ignored. These warnings are usually about 34 34 deprecated, but not invalid, use of the C or C++ syntax. C standards change 35 fairly often, and some packages still use the older standard. This is not a36 problem, but does prompt the warning.</para>35 fairly often, and some packages have not yet been updated. This is not a 36 serious problem, but it does cause the warnings to appear.</para> 37 37 </listitem> 38 38 … … 70 70 71 71 <listitem override='bullet'><para><command>/usr/bin/yacc</command> is a 72 symbolic link to <command>bison</command> ora small script that72 symbolic link to <command>bison</command>, or to a small script that 73 73 executes bison.</para></listitem> 74 74 … … 77 77 78 78 <important> 79 <para> To re-emphasize the build process:</para>79 <para>Here is a synopsis of the build process.</para> 80 80 81 81 <orderedlist numeration="arabic" spacing="compact"> 82 82 <listitem> 83 83 <para>Place all the sources and patches in a directory that will be 84 accessible from the chroot environment such as84 accessible from the chroot environment, such as 85 85 <filename class="directory">/mnt/lfs/sources/</filename>.<!-- Do 86 86 <emphasis>not</emphasis> put sources in … … 88 88 </listitem> 89 89 <listitem> 90 <para>Change to the sourcesdirectory.</para>90 <para>Change to the <filename class="directory">/mnt/lfs/sources/</filename> directory.</para> 91 91 </listitem> 92 92 <listitem id='buildinstr' xreflabel='Package build instructions'> … … 98 98 <xref linkend="chapter-temporary-tools"/>, ensure you are 99 99 the <emphasis>lfs</emphasis> user when extracting the package.</para> 100 <para>All methods to get the source code tree being built101 in-position, except extracting the package tarball, are not102 supported. Notably, using <command>cp -R</command>to copy the100 <para>Do not use any method except the <command>tar</command> command 101 to extract the source code. Notably, using the <command>cp -R</command> 102 command to copy the 103 103 source code tree somewhere else can destroy links and 104 timestamps in the sources tree and cause building 105 failure.</para> 104 timestamps in the source tree, and cause the build to fail.</para> 106 105 </listitem> 107 106 <listitem> … … 110 109 </listitem> 111 110 <listitem> 112 <para>Follow the book'sinstructions for building the package.</para>111 <para>Follow the instructions for building the package.</para> 113 112 </listitem> 114 113 <listitem> 115 <para>Change back to the sources directory .</para>114 <para>Change back to the sources directory when the build is complete.</para> 116 115 </listitem> 117 116 <listitem>
Note:
See TracChangeset
for help on using the changeset viewer.