Changeset 6a8ff5c
- Timestamp:
- Feb 21, 2006, 2:03:39 AM (19 years ago)
- Children:
- 4f2f16a
- Parents:
- 960d87a
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
appendices/acronymlist.xml
r960d87a r6a8ff5c 327 327 <term><emphasis role="bold">LSB</emphasis></term> 328 328 <listitem> 329 <para>Linux Standard sBase</para>329 <para>Linux Standard Base</para> 330 330 </listitem> 331 331 </varlistentry> -
final-preps/abouttestsuites.xml
r960d87a r6a8ff5c 28 28 29 29 <note> 30 <para>Experience has shown that there is little to be gained 31 from running the test suites in <xref 32 linkend="chapter-testsuite-tools"/>. There can be no escaping the fact 33 that the host system always exerts some influence on the tests in that 34 chapter, often causing inexplicable failures. Because the tools built 35 in <xref linkend="chapter-testsuite-tools"/> are temporary and 36 eventually discarded, we do not recommend running the test suites in 37 <xref linkend="chapter-testsuite-tools"/> for the average reader. The 38 instructions for running those test suites are provided for the 39 benefit of testers and developers, but they are strictly 40 optional.</para> 30 <para>It is not possible to run testsuites when cross-compiling, so there 31 are no instructions given for running testsuites until 32 <xref linkend="chapter-building-system"/>.</para> 41 33 </note> 42 34 … … 46 38 most likely cause is that the host system does not have the 47 39 <systemitem class="filesystem">devpts</systemitem> file system set up 48 correctly. This issue is discussed in greater detail in <xref49 linkend="chapter-testsuite-tools"/>.</para>40 correctly. This issue is discussed in greater detail at 41 <ulink url="http://www.linuxfromscratch.org/lfs/faq.html#no-ptys"/>.</para> 50 42 51 43 <para>Sometimes package test suites will fail, but for reasons which the -
final-preps/settingenviron.xml
r960d87a r6a8ff5c 56 56 the shell will always search the <envar>PATH</envar> when a program is to 57 57 be run. As such, the shell will find the newly compiled tools in 58 <filename class="directory">$LFS/ tools</filename> as soon as they are58 <filename class="directory">$LFS/cross-tools</filename> as soon as they are 59 59 available without remembering a previous version of the same program in a 60 60 different location.</para> -
final-system/common/inetutils.xml
r960d87a r6a8ff5c 25 25 <seglistitem> 26 26 <seg>Bash, Binutils, Coreutils, Diffutils, GCC, Glibc, Grep, 27 Make, Ncurses, Patch, and Sed</seg>27 Make, Ncurses, Patch, Sed, and Zlib</seg> 28 28 </seglistitem> 29 29 </segmentedlist> -
final-system/common/vim.xml
r960d87a r6a8ff5c 114 114 115 115 <indexterm zone="conf-vim"> 116 <primary sortas="e-/etc/vim">/etc/vim </primary>116 <primary sortas="e-/etc/vim">/etc/vimrc</primary> 117 117 </indexterm> 118 118 -
introduction/common/how.xml
r960d87a r6a8ff5c 20 20 21 21 <para>As an alternative to installing an entire separate distribution 22 onto your machine, and if your host machine is x86 based,you may wish to22 onto your machine, you may wish to 23 23 use the Linux From Scratch LiveCD. The CD works well as a host system, 24 24 providing all the tools you need to successfully follow the instructions -
introduction/common/resources.xml
r960d87a r6a8ff5c 39 39 <title>News Server</title> 40 40 41 <para> The Linux From Scratch is no longer available.41 <para> The Linux From Scratch News Server is no longer available. 42 42 Please use the other support methods listed on this page 43 43 </para> -
temp-system/common/introduction.xml
r960d87a r6a8ff5c 17 17 with more user convenience than a minimum environment would.</para> 18 18 19 <para>There are two steps in building this minimal system. The first 20 step is to build a new and host-independent toolchain (compiler, 21 assembler, linker, libraries, and a few useful utilities). The second 22 step uses this toolchain to build the other essential tools.</para> 23 24 <para>The files compiled in this chapter will be installed under the 19 <para>The tools in this chapter are cross-compiled using the toolchain in /cross-tools. The files compiled in this chapter will be installed under the 25 20 <filename class="directory">$LFS/tools</filename> directory to keep 26 21 them separate from the files installed in <xref
Note:
See TracChangeset
for help on using the changeset viewer.