cvs commit: www/lfs faq.html packages.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Sat Sep 20 08:53:22 PDT 2003


jeroen      03/09/20 09:53:22

  Modified:    lfs      faq.html packages.html
  Log:
  Update packages page
  
  Revision  Changes    Path
  1.21      +4 -0      www/lfs/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvsroot/www/lfs/faq.html,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- faq.html	17 Sep 2003 16:52:13 -0000	1.20
  +++ faq.html	20 Sep 2003 15:53:22 -0000	1.21
  @@ -316,9 +316,13 @@
   				<li>/usr/bin/env: /static/bin/bash: No such file or directory</li>
   				<li>gcc: No such file or directory</li>
   			</ul>
  +			<p>If you're using LFS-4.1 or earlier:</p>
   			<p>They usually occur when trying to enter (or shortly after entering) chroot in Chapter 6, and are caused by trying to run a dynamically linked binary at that point. You can check by running file on the binary. For example:<code>file $LFS/static/bin/bash</code>.</p>
   			<p>If it doesn't say something about "statically linked", there is a problem.</p>
   			<p>The solution is to go back to Chapter 5, delete and re-extract the source if you haven't already, and recompile the affected package. And this time, take extra care with the instructions for compiling it statically.</p>
  +			<p>If you're using LFS-5.x or later:</p>
  +			<p>With the new Ch 5 build procedure, the most common cause of this problem is forgetting to apply the specs patch.</p>
  +			<p>What happens is that the path to the dynamic linker embedded inside the executable is still pointing at /lib/ld-linux.so.2 and when one goes to run the binary inside the chroot where /lib/ld-linux.so.2 does not exist yet, the very unhelpful <code>No such file or directory</code> error message is shown.</p>
   		</dd>
   	<dt id="configure-no-such-file">bash: ./configure: No such file or directory</dt>
   		<dd>
  
  
  
  1.51      +2 -2      www/lfs/packages.html
  
  Index: packages.html
  ===================================================================
  RCS file: /home/cvsroot/www/lfs/packages.html,v
  retrieving revision 1.50
  retrieving revision 1.51
  diff -u -r1.50 -r1.51
  --- packages.html	17 Sep 2003 16:52:13 -0000	1.50
  +++ packages.html	20 Sep 2003 15:53:22 -0000	1.51
  @@ -43,9 +43,9 @@
   	<h3 id="freshmeat">Freshmeat</h3>
   		<p>The first is to hunt down all the packages in <a href="view/stable/chapter04/packages.html">the book</a>. This is a laborious click-and-point process, not always succesfull since older versions of packages may become less available. In that case the <a href="http://lfs.sourceforge.net/wiki/UpdatedVersions" title="Updated Versions">LFS wiki</a> may have an answer. If it hasn't, try to <a href="http://www.google.com/">google</a> for the package (for example, <a href="http://www.google.com/search?q=bash-2.05a.tar.gz">bash-2.05a.tar.gz</a>). You can also use the sources from your Linux distribution. <a href="http://www.debian.org/">Debian</a> has an excellent <a href="http://www.debian.org/distrib/packages">search page</a> from which you can download the original sources of packages. This method is probably only useful if you really must have all the latest versions (and in that case, check out the <a href="../faq/#why-not-version">FAQ</a>).</p>
   	<h3 id="wget">wget</h3>
  -		<p>The second is a <a href="http://www.gnu.org/software/wget/wget.html" title="GNU wget webpage">wget</a> script. Choose between the <a href="wget/lfs-stable.wget" title="stable versions">stable</a> or the <a href="wget/lfs-cvs.wget" title="only for CVS or your own risk">CVS <em>(currently not up-to-date!)</em></a> list.  We can only guarantee that the lfs-stable.wget script is fully in sync with the stable book release. To use it, enter <code>wget -i lfs-stable.wget</code>.</p>
  +		<p>The second is a <a href="http://www.gnu.org/software/wget/wget.html" title="GNU wget webpage">wget</a> script. We provide <a href="wget/">multiple wget scripts<a>, one for each release. Please beware that the <a href="wget/lfs-cvs.wget">CVS wget script</a> is often out of date. Send your updated version to the <a href="http://linuxfromscratch.org/mailman/listinfo/website"> the website mailinglist</a>. To use a wget script, enter <code>wget -i lfs-stable.wget</code>.</p>
   	<h3 id="p2p">Peer-2-peer networks</h3>
  -		<p>This is really the preferred distribution channel, since it offloads our servers. At the moment this method requires a bit of patience, since not many people use it yet. If you have some bandwidth to spare, you may wish to get the package via one of the FTP or HTTP mirrors (see below) and add it to your P2P shared directory. <strong>The more people who download and share it, the faster your download will go.</strong> Please don't delete or move the package after you've downloaded it, but keep it in your shared folder for other people. </p>
  +		<p>This is really the preferred distribution channel, since it offloads our servers. At the moment this method requires a bit of patience, since not many people use it yet. If you have some bandwidth to spare, you may wish to get the package via one of the FTP or HTTP mirrors (see below) and add it to your P2P shared directory. <em class="highlight">The more people who download and share it, the faster your download will go.</em> So be kind to the community and don't delete or move the package after you've downloaded it. Keep it in your shared folder for other people. </p>
   	<p>We provide links for the following packages:</p>
   	<h4>The LFS 4.1 package</h4>
   	<h5>A tarball of all files required for LFS 4.1:</h5>
  
  
  



More information about the website mailing list