Changeset 1e6acd6
- Timestamp:
- 09/22/2002 03:01:40 AM (22 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- b4a5535
- Parents:
- f8decc78
- Location:
- chapter02
- Files:
-
- 6 edited
-
aboutlfs.xml (modified) (2 diffs)
-
aboutsbus.xml (modified) (2 diffs)
-
askforhelp.xml (modified) (6 diffs)
-
download.xml (modified) (1 diff)
-
install.xml (modified) (4 diffs)
-
platform.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
chapter02/aboutlfs.xml
rf8decc78 r1e6acd6 10 10 the LFS partition is mounted on /mnt/lfs.</para> 11 11 12 <para> For example when you are told to run a command like12 <para>When you are told to run a command like 13 13 <userinput>./configure --prefix=$LFS/static</userinput> you actually have to 14 14 execute <userinput>./configure --prefix=/mnt/lfs/static</userinput>.</para> … … 23 23 <para><screen><userinput>export LFS=/mnt/lfs</userinput></screen></para> 24 24 25 <para>Now, if you are told to run a command like <userinput>./configure 26 --prefix=$LFS/static</userinput> you can type that literally. Your shell will 25 <para>Now, if you are told to run a command like </para> 26 27 <para><screen><userinput>./configure --prefix=$LFS/static</userinput></screen></para> 28 29 <para>you can type that literally. Your shell will 27 30 replace $LFS with /mnt/lfs when it processes the command line (meaning 28 31 when you hit enter after having typed the command).</para> -
chapter02/aboutsbus.xml
rf8decc78 r1e6acd6 7 7 times like anybody else?</para> 8 8 9 <para>The biggest problem is that times cannot be ac urate, not even a9 <para>The biggest problem is that times cannot be accurate, not even a 10 10 little bit. So many people install LFS on so many different systems, the 11 11 times it takes to compile something varies too much. One package may take … … 23 23 a close approximation of how long GCC will take on your system.</para> 24 24 25 <para>Note: SBUs don't work on SMP machines. We've seen that SBUs don't 26 work well on SMP based machines. So all bets are off if you're lucky enough 27 to have an SMP setup.</para> 25 <para>Note: We've seen that SBUs don't work well on SMP based machines. So 26 all bets are off if you're lucky enough to have an SMP setup.</para> 28 27 29 28 </sect1> -
chapter02/askforhelp.xml
rf8decc78 r1e6acd6 5 5 <para>If you encounter a problem while using this book, and your problem 6 6 is not listed in the FAQ, you will find that most of the people on Internet 7 Relay Chat (IRC) and on the mailing lists are willing to help you. (An7 Relay Chat (IRC) and on the mailing lists are willing to help you. An 8 8 overview of the LFS mailing lists can be found in 9 <xref linkend="ch01-maillists"/>. )To assist us in diagnosing and solving9 <xref linkend="ch01-maillists"/>. To assist us in diagnosing and solving 10 10 your problem, include as much relevant information as possible in your 11 11 request for help.</para> … … 19 19 <itemizedlist> 20 20 <listitem><para>the version of the book you are using (being &version;),</para></listitem> 21 <listitem><para>the package or section you are having problems with,</para></listitem>21 <listitem><para>the package or section giving you problems,</para></listitem> 22 22 <listitem><para>the exact error message or symptom you are receiving,</para></listitem> 23 23 <listitem><para>whether you have deviated from the book at all.</para></listitem> … … 35 35 <para>When something goes wrong during the stage where the configure 36 36 script is run, look at the last lines of the 37 <filename>config.log</filename>. This file contains possibleerrors38 encountered during configure which aren't alwaysprinted to the screen.37 <filename>config.log</filename>. This file may contain errors 38 encountered during configure which weren't printed to the screen. 39 39 Include those relevant lines if you decide to ask for help.</para> 40 40 … … 46 46 <para>To help us find the cause of the problem, both screen output and 47 47 the contents of various files are useful. The screen output from both 48 the ./configure script and when make is run can be useful. Don't49 blindly include the whole thing but on the other hand, don't include too 50 little.As an example, here is some screen output from make:</para>48 the ./configure script and the make run can be useful. Don't blindly 49 include the whole thing but on the other hand, don't include too little. 50 As an example, here is some screen output from make:</para> 51 51 52 52 <para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" … … 70 70 isn't enough for us to diagnose the problem because it only tells us 71 71 that <emphasis>something</emphasis> went wrong, not 72 <emphasis>what</emphasis> went wrong. The whole section as73 quoted aboveis what should be included to be helpful, because it72 <emphasis>what</emphasis> went wrong. The whole section, as 73 in the example above, is what should be included to be helpful, because it 74 74 includes the command that was executed and the command's error 75 75 message(s).</para> … … 78 78 has been written by Eric S. Raymond. It is available online at <ulink 79 79 url="http://www.tuxedo.org/~esr/faqs/smart-questions.html"/>. 80 Read and follow the hints in th isdocument and you are much more likely80 Read and follow the hints in that document and you are much more likely 81 81 to get a response to start with and also to get the help you actually 82 82 need.</para> -
chapter02/download.xml
rf8decc78 r1e6acd6 7 7 8 8 <para>While it doesn't matter at all where you save the downloaded 9 packages, we recommend storing it at least on the LFS partition. This just 10 makes sense because you would still have access to those files when you boot 11 into the LFS system. $LFS/usr/src is just a logical place to store source 12 code, but by no means a requirement. You may even want to create a 13 subdirectory under $LFS/usr/src for tarball storage. That way you can 14 separate tarballs from temporary build directories, but again that's up 15 to you.</para> 9 packages, we recommend storing it at least on the LFS partition. This 10 just makes sense because you need to have access to those those files 11 when you chroot to $LFS and when you boot into the LFS system, although 12 access when booted to $LFS could be handled other ways. $LFS/usr/src is 13 just a logical place to store source code, but by no means a requirement. 14 You may even want to create a subdirectory under $LFS/usr/src for tarball 15 storage. That way you can separate tarballs from temporary build 16 directories, but again that's up to you.</para> 16 17 17 18 <para>The next chapter contains a list of all the packages that need to be -
chapter02/install.xml
rf8decc78 r1e6acd6 39 39 <para>If a file is just tar'ed, it is unpacked by running:</para> 40 40 41 <para><screen><userinput>tar xvf filename.tar</userinput></screen></para>41 <para><screen><userinput>tar -xvf filename.tar</userinput></screen></para> 42 42 43 43 <para>When an archive is unpacked, a new directory will be created under the … … 50 50 <para>From time to time you will be dealing with single files such as patch 51 51 files. These files are generally gzip'ed or bzip2'ed. Before such files 52 can be used they need to be uncompressed first.</para>52 can be used they need to be uncompressed.</para> 53 53 54 54 <para>If a file is gzip'ed, it is unpacked by running:</para> … … 64 64 can be kept. We highly recommend deleting it. If you don't do this and 65 65 try to re-use the same source later on in the book (for example re-using 66 the source trees from Chapter 5 for usein Chapter 6), it may not work66 the source trees from Chapter 5 in Chapter 6), it may not work 67 67 as you expect it to. Source trees from Chapter 5 will have your host 68 68 distribution's settings, which don't always apply to the LFS system 69 after you enter the chroot 'edenvironment. Even running something like69 after you enter the chroot environment. Even running something like 70 70 <emphasis>make clean</emphasis> doesn't always guarantee a clean source 71 71 tree.</para> … … 76 76 77 77 <para>There is one exception; the kernel source tree. Keep it around as you 78 will need it later in this book when building a kernel. Nothing will use79 the kernel tree so the source tree won't be in your way. If, however,80 you are short of disk space, you can remove the kernel tree and re-untar 81 it later when required.</para>78 will need it later in this book when building a kernel. Nothing before then 79 will use the kernel tree, so the source tree won't be in your way. If, 80 however, you are short of disk space, you can remove the kernel tree and 81 re-untar it later when required.</para> 82 82 83 83 </sect1> -
chapter02/platform.xml
rf8decc78 r1e6acd6 3 3 <?dbhtml filename="platform.html" dir="chapter02"?> 4 4 5 <para>LFS intends to be as far as possible platform independent.Having6 said that, the main LFS development work occurs on the x86 platform. 5 <para>LFS intends to be, as far as possible, platform independent. Having 6 said that, the main LFS development work occurs on the x86 platform. We 7 7 attempt to include information where possible on differences for other 8 8 platforms such as PPC. If you come across a problem compiling which is
Note:
See TracChangeset
for help on using the changeset viewer.
