Subversion Repositories svn LFS-FR

Rev

Rev 7247 | Rev 7249 | Go to most recent revision | Blame | Compare with Previous | Last modification | View Log | RSS feed

# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 8.0\n"
"POT-Creation-Date: 2017-03-12 09:56+0100\n"
"PO-Revision-Date: 2017-03-01 20:00+0100\n"
"Last-Translator: roptat <roptat@lepiller.eu>\n"
"Language-Team: lfs-fr <lfs-traducfr@linuxfromscratch.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: Content of: <h1>
#: faq-en.html:2
msgid "LFS Frequently Asked Questions"
msgstr ""

#. type: Content of: <p>
#: faq-en.html:3
msgid ""
"The FAQ is divided in three documents. The <a "
"href=\"/faq/index.html\">General FAQ</a> has links to all questions and "
"answers. The <a href=\"/lfs/faq.html\">LFS FAQ</a> is a selection of "
"LFS-specific FAQ's and the <a href=\"/blfs/faq.html\">BLFS FAQ</a> is a "
"selection of BLFS-specific FAQ's."
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:9
msgid "<a href=\"#fre\">Frequently Requested Enhancements</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:11
msgid "<a href=\"#add-grub\">Why not use LILO instead of GRUB?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:12
msgid ""
"<a href=\"#why-not-new-lilo\">Why not upgrade LILO to the latest "
"version?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:13
msgid "<a href=\"#why-not-faq\">Why not include the FAQ in the book?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:14
msgid "<a href=\"#why-vim\">Why is vim in the book?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:15
msgid "<a href=\"#hjl-binutils\">Why is HJL's Binutils not in the book?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:16
msgid ""
"<a href=\"#why-not-package-management\">Why isn't some package manager in "
"the book?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:17
msgid ""
"<a href=\"#no-poweroff\">How do I make my machine poweroff when shut "
"down?</a>"
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:19
msgid "<a href=\"#resources\">When reading and building LFS</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:21
msgid "<a href=\"#what-dist\">What distribution should I use to start from?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:22
msgid "<a href=\"#kernel-modules\">How do I compile a kernel or set up modules?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:23
msgid "<a href=\"#gcc-warnings\">Are compiler warnings from GCC bad?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:24
msgid ""
"<a href=\"#dirty-sources\">Do I need to keep the source after "
"installing?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:25
msgid ""
"<a href=\"#really-small\">How do I make that really small install the book "
"mentions?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:26
msgid ""
"<a href=\"#procs-lfs\">Is there information about building LFS on other "
"processors?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:27
msgid "<a href=\"#cross-compile\">How do I cross compile LFS?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:28
msgid "<a href=\"#dos-text\">What's a DOS format text file?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:29
msgid ""
"<a href=\"#wget\">Is there a way to download all current files at one "
"time?</a>"
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:31
msgid "<a href=\"#generrors\">General compilation errors</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:33
msgid "<a href=\"#gnu-patches\">I used a patch from GNU to upgrade. Is that OK?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:34
msgid ""
"<a href=\"#optimizations\">When using optimization flags (setting "
"CFLAGS)</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:35
msgid ""
"<a href=\"#config-hang-size_t\">Why does configure hang at &quot;checking "
"for signed size_t type...&quot;?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:36
msgid ""
"<a href=\"#dirty-sources\">I didn't delete the source tree after my last "
"attempt. Do I need to?</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:37
msgid "<a href=\"#perm-denied\">I'm getting `/dev/null: Permission denied'</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:38
msgid "<a href=\"#sig11\">signal 11 (internal error: Segmentation fault)</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:39
msgid "<a href=\"#any-no-such-file\">No such file or directory</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:40
msgid ""
"<a href=\"#configure-no-such-file\">bash: ./configure: No such file or "
"directory</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:41
msgid ""
"<a href=\"#bad-interpreter-permission-denied\">./configure: bad interpreter: "
"Permission denied</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:42
msgid "<a href=\"#conf-guess-fail\">configure can't guess my host type.</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:43
msgid "<a href=\"#config-not-gnu-c\">checking whether we are using GNU C... no</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:44
msgid ""
"<a href=\"#no-ptys\">The system has no more ptys.  Ask your system "
"administrator to create more.</a>"
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:46
msgid "<a href=\"#packerrors\">Package-specific errors</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:48
msgid ""
"<a href=\"#unknown-pseudo-op-hidden\">GCC: Error: Unknown pseudo-op: "
"`.hidden'</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:49
msgid "<a href=\"#glibc-awk-fail\">Glibc fails and mentions BEGIN and END.</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:50
msgid ""
"<a href=\"#glibc-nss\">Glibc compilation errors out due to a missing nss.h "
"header file</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:51
msgid ""
"<a href=\"#cpp-fails-sanity-check\">Ncurses: C++ preprocessor "
"&quot;/lib/cpp&quot; fails sanity check</a>"
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:53
msgid "<a href=\"#confboot\">Configuration and booting issues</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:55
msgid ""
"<a href=\"#unable-to-mount-root\">Kernel panic: VFS: unable to mount root "
"fs</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:56
msgid ""
"<a href=\"#respawning-too-fast\">init: Id &quot;1&quot; respawning too fast: "
"disabled for 5 minutes</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:57
msgid ""
"<a href=\"#char-major-10-135\">modprobe: Can't locate module "
"char-major-10-135</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:58
msgid "<a href=\"#no-dev-rtc\">modprobe: Can't locate module /dev/rtc</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:59
msgid "<a href=\"#eth0-unknown-interface\">eth0:unknown interface</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:60
msgid "<a href=\"#spurious-8259A-interrupt\">spurious 8259A interrupt: IRQ14</a>"
msgstr ""

#. type: Content of: <ul><li>
#: faq-en.html:61
msgid ""
"<a href=\"#less-prints-ad\">Why does less (and therefore man) print "
"&lt;AD&gt; instead of hyphens?</a>"
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:65
msgid "Frequently Requested Enhancements"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:67
msgid "Why not use LILO instead of GRUB?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:69
msgid ""
"Since LFS-5.0, released 5 November 2003, LFS uses Grub instead of Lilo. Grub "
"was chosen because it doesn't require reinstallation after a kernel upgrade "
"and has a very nice rescue console."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:72
msgid ""
"If your current setup uses LILO or you'd like to use it anyway, you can, but "
"beware you will also need to install BIN86 and, for the latest LILO "
"versions, NASM. However, don't preach about it on the LFS mailinglists, "
"since we've had many flamewars about it in the past."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:78
msgid "Why not include the FAQ in the book?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:80
msgid "Marc Heerdink may have said it best in a post to lfs-dev:"
msgstr ""

#. type: Content of: <dl><dd><blockquote><p>
#: faq-en.html:81
msgid ""
"The problem is that the FAQ is a dynamic document. The FAQ for a book "
"release is released only after the book version itself, because the FAQ is "
"updated to reflect the Qs asked about the current version of the book. A "
"link is better, since you'll always have the most up-to-date answers handy."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:87
msgid "Why is vim in the book?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:89
msgid ""
"This is fairly well discussed in the thread starting at <a "
"href=\"http://linuxfromscratch.org/pipermail/lfs-dev/2002-February/023030.html\">http://linuxfromscratch.org/pipermail/lfs-dev/2002-February/023030.html</a>."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:92
msgid "Why is HJL's Binutils not in the book?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:94
msgid ""
"The binutils release that you typically find on ftp.gnu.org is commonly "
"known as the &quot;FSF&quot; binutils. Noted hacker H.J. Lu also makes "
"releases out of the main CVS repository and these are commonly known as the "
"&quot;HJL&quot; binutils and can usually be found on ftp.kernel.org. Debate "
"often arises over which version to use due to the fact that most mainstream "
"distros tend to use the HJL releases even though they are typically marked "
"as &quot;beta&quot;."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:102
msgid "Here is our interpretation of the differences between the two:"
msgstr ""

#. type: Content of: <dl><dd><h4>
#: faq-en.html:103
msgid "HJL:"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:105
msgid "For Linux OS only"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:106
msgid "Marked as &quot;beta&quot;"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:107
msgid "Closely follows the CVS HEAD"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:108
msgid "Usually contains the latest subtle bug fixes"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:109
msgid "Usually has latest bug fixes for non-x86 arch's"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:110
msgid ""
"Usually a new release every time a significant bug that affects Linux gets "
"fixed"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:111
msgid "Theoretically less stable due to newness of code"
msgstr ""

#. type: Content of: <dl><dd><h4>
#: faq-en.html:113
msgid "FSF:"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:115
msgid "Supports more OS's (not only Linux)"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:116
msgid "Latest code from the stable branch of CVS"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:117
msgid ""
"Sometimes not up-to-date WRT to the latest bleeding edge kernel, gcc and "
"glibc subtleties"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:118
msgid ""
"Often includes features backported from the CVS HEAD after a period of "
"testing"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:119
msgid "Theoretically more stable"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:121
msgid ""
"You'll notice in the above points words like &quot;usually&quot; and "
"&quot;sometimes&quot;. This demonstrates how the situation can be different "
"depending on which particular point in time you happen to be referring "
"to. For example, from time to time there will be a new bleeding edge feature "
"in gcc or glibc that requires support from binutils. During these times you "
"will often hear the developers say &quot;you must be using the latest HJL "
"binutils version x.y.z.a.b&quot;."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:129
msgid "The only way to correctly choose the most appropriate release to use is to:-"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:131
msgid ""
"Stay abreast of the issues on the project mailing lists of the core "
"toolchain packages"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:132
msgid ""
"Have a large dose of technical prowess and/or programming talent to "
"understand all the issues"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:133
msgid "Test like crazy by running the test suites"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:134
msgid "Test like crazy by building full systems"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:136
msgid ""
"The facts of the matter are that the core toolchain packages are all very "
"tightly bound and must be tested to ensure they work together. You basically "
"have to build a full working distro and test every aspect of it to be fully "
"satisfied."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:140
msgid ""
"If you follow the project mailing lists of the core toolchain packages for "
"long enough, you'll soon realise that the developers do not care much "
"whether a particular release of &quot;Package A&quot; works with a "
"particular release of &quot;Package B&quot;. In other words, release "
"coordination between the projects is not a priority.  In reality, this means "
"that Alan Cox is right when he says that you cannot just go to ftp.gnu.org "
"and grab the latest of everything and always expect it to just work."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:149
msgid "Why isn't some package manager in the book?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:151
msgid ""
"Package management - beyond that provided by tarballs and makefiles - is "
"beyond the scope of the book. If nothing else does, the number of different "
"\"solutions\" should hint at some of the reasons."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:155
msgid "Here are a few of the options:"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:157
msgid ""
"No package management is really necessary. Unless it is desirable to monitor "
"package file placement minutely, any package large enough to warrent removal "
"for disk space reasons can be installed in /opt as detailed by the FHS "
"(perhaps in /opt/foo-x.x with a link from /opt/foo), and new releases can "
"usually be installed over the old, although major upgrades and libraries are "
"generally best done by rebuilding the system from the bottom up."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:165
msgid ""
"RPM, the Redhat Package Manager, is used by a number of distributions. It is "
"available from <a href=\"http://www.rpm.org/\">http://www.rpm.org/</a>, and "
"there is an <a href=\"../hints/downloads/files/\">RPM Hint</a> to help with "
"installation."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:170
msgid "There are several implementations of symlink style package management:"
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:172
msgid ""
"Epkg is available from <a "
"href=\"http://www.encap.org/epkg/\">http://www.encap.org/epkg/</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:173
msgid ""
"Graft is available from <a href=\"http://peters.gormand.com.au/Home/tools\" "
">http://peters.gormand.com.au/Home/tools</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:174
msgid ""
"GNU Stow is available from <a "
"href=\"http://www.gnu.org/software/stow/\">http://www.gnu.org/software/stow/</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:175
msgid ""
"And several more are listed in the Graft documentation at <a "
"href=\"http://peters.gormand.com.au/Home/tools/graft/graft-html#research\">http://peters.gormand.com.au/Home/tools/graft/graft-html#research</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:179
msgid ""
"The NetBSD package manager, pkgsrc, is available on other systems including "
"Linux. It is at <a "
"href=\"ftp://ftp.netbsd.org/pub/pkgsrc/stable/\">ftp://ftp.netbsd.org/pub/pkgsrc/stable/</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:182
msgid ""
"Originally based on a script written by LFS' own Gerard Beekmans, "
"install-log records a list of files installed by a package as the package is "
"installed. It is available from <a "
"href=\"http://install-log.sourceforge.net/\">http://install-log.sourceforge.net/</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:186
msgid ""
"Gerard has since made additions to his script. It is available from <a "
"href=\"http://linuxfromscratch.org/~gerard/log-install\">http://linuxfromscratch.org/~gerard/log-install</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:189
msgid ""
"CheckInstall attempts log system calls made by \"make install\".  It is "
"available from <a "
"href=\"http://asic-linux.com.mx/%7Eizto/checkinstall/\">http://asic-linux.com.mx/~izto/checkinstall/</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:192
msgid ""
"pkgutils, used by the CRUX distribution, is available from <a "
"href=\"http://www.fukt.bsnet.se/%7Eper/pkgutils/\">http://www.fukt.bsnet.se/~per/pkgutils/</a>."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:194
msgid ""
"There are some <a href=\"../hints/downloads/files/\">hints</a> available for "
"package managers."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:196
msgid ""
"If you have an addition to the list, please do email its id, URL, and other "
"information, to the FAQ maintainer or an appropriate LFS mailing list so it "
"can be added here."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:200
msgid "How do I make my machine poweroff when shut down?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:202
msgid ""
"Power Management is a kernel function, you need to enable it in the "
"kernel. In the 2.4 kernel, you have to enable the options for <code>Power "
"Management Support</code> under <code>General Setup</code>. For older "
"machines, you'll probably want the APM options, newer machines often require "
"ACPI. Make sure that either APM or ACPI be enabled in the kernel, but "
"definitely <strong>not</strong> both at the same time - this has been known "
"to cause problems such as neither actually taking effect. Also try disabling "
"SMP if you only have one processor; it's also known to prevent a proper "
"poweroff.  Make sure you read the help with each option."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:212
msgid ""
"After rebooting into the new kernel you should be able to poweroff your "
"machine with the command <code>shutdown -h now</code> or "
"<code>poweroff</code> (also read <code>man shutdown</code> and <code>man "
"halt</code>). If you compiled APM or ACPI as modules, make sure they are "
"loaded before you try to power off.  Some machines require that APM or ACPI "
"is compiled into the kernel because it needs to be initialised at boottime."
msgstr ""

#. type: Content of: <p>
#: faq-en.html:221 faq-en.html:352 faq-en.html:560 faq-en.html:619
msgid "<a href=\"#lfsfaq\">Back to the top.</a>"
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:223
msgid "When reading and building LFS"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:225
msgid "What distribution should I use to start from?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:227
msgid ""
"Most relatively recent distributions should be fine. Do not use Fedora Core "
"4 as its version of GCC does not work with the current stable version of "
"LFS. Make sure you have installed and/or updated the development "
"packages. (Look for ones starting in \"gcc\", \"glibc\", or \"libstdc++\" or "
"ending in \"-dev\".). If you want to use LFS as your main system and you "
"wish to install it without first installing a distribution, try <a "
"href=\"http://www.knopper.net/knoppix/index-en.html\">Knoppix</a>."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:236
msgid "How do I compile a kernel or set up modules?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:238
msgid ""
"In addition to the kernel documentation at <a "
"href=\"file:///usr/src/linux/Documentation\">/usr/src/linux/Documentation</a> "
"or wherever you unpacked your kernel source and the help in kernel config "
"tool (make menuconfig), see the Module-HOWTO at <a "
"href=\"http://www.tldp.org/HOWTO/Module-HOWTO/\">http://www.tldp.org/HOWTO/Module-HOWTO/</a>."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:244
msgid "Are compiler warnings from GCC bad?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:246
msgid "Short answer: no."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:247
msgid ""
"Long answer: probably, but only to someone working on the package you're "
"trying to compile. Mostly, everything will be fine unless make quits with an "
"error."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:250
msgid "Here's an example:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:252
msgid "sk ~/tmp $ cat &gt; Makefile"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:253
msgid "main:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:254 faq-en.html:258 faq-en.html:266
msgid "gcc main.c"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:255 faq-en.html:263
msgid "sk ~/tmp $ cat &gt; main.c"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:256
msgid "void main() { exit(0); }"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:257 faq-en.html:265
msgid "sk ~/tmp $ make"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:259 faq-en.html:267
msgid "<strong>main.c: In function `main':</strong>"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:260
msgid "<strong>main.c:1: warning: return type of `main' is not `int'</strong>"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:261
msgid "sk ~/tmp $ ######## that worked ########"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:262 faq-en.html:271
msgid "sk ~/tmp $"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:264
msgid "int main() { e<span class=\"strong\">xx</span>it(0) }"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:268
msgid "<strong>main.c:1: parse error before `}'</strong>"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:269
msgid "<strong>make: *** [main] Error 1</strong>"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:270
msgid "sk ~/tmp $ ######## that failed ########"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:274
msgid "How do I make that really small install the book mentions?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:276
msgid ""
"Gerard describes the process of making a 5MB LFS install in <a "
"href=\"http://linuxfromscratch.org/pipermail/lfs-support/2001-October/000202.html\">an "
"email to lfs-support</a>, and there are links to many resources in <a "
"href=\"http://linuxfromscratch.org/pipermail/lfs-support/2002-June/007255.html\">a "
"post by Cor Lem</a> and a reply to it."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:283
msgid "Is there information about building LFS on other processors?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:285
msgid ""
"For information about building LFS for a wide array of systems, take a look "
"at the <a href=\"http://trac.clfs.org/wiki/read\">Cross-LFS branch</a> of "
"LFS."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:289
msgid ""
"For Alpha systems, Kelledin maintains a list of fixes for building on the "
"Alpha platform at <a "
"href=\"http://skarpsey.dyndns.org/alpha-lfs/alpha.html\">http://skarpsey.dyndns.org/alpha-lfs/alpha.html</a>."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:293
msgid "How do I cross compile LFS?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:295
msgid ""
"It's often useful to compile LFS for one machine on another machine. Say "
"using that fast 1Ghz Athlon to build an install for an old 486. While this "
"is technically not cross compiling, binaries compiled for the Athlon cannot "
"be run on the 486 because binaries compiled for the newer processor use "
"features the older processor doesn't have."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:301
msgid ""
"The LFS book specifically for cross compiling is the <a "
"href=\"http://trac.clfs.org/wiki/read\">Cross-LFS</a> book.  Another source "
"of information would be the <a "
"href=\"/hints/downloads/files/\">cross-compiling hint</a>."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:306
msgid "What's a DOS format text file?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:308
msgid "It has to do with the characters used to end lines."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:309
msgid "There are two that may be used:"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:311
msgid ""
"Line Feed: (LF) Octal:012 Decimal:10 Hex:0A C Style Escape:'\\n' Moves down "
"one line."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:312
msgid ""
"Carriage Return: (CR) Octal:015 Decimal:13 Hex:0D C Style Excape:'\\r' Move "
"to the left margin."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:314
msgid ""
"Unix, DOS, and MacOS each use a different combination to end lines in text "
"files:"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:316
msgid ""
"Unix: LF only. This is why when a Unix format text file is sent to a printer "
"raw, it prints out"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:317
msgid "&nbsp;&nbsp;like"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:318
msgid "&nbsp;&nbsp;&nbsp;&nbsp;stairs"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:319
msgid "&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;steps."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:320
msgid ""
"DOS: CRLF both. Which is why if you do \"cat -v\" on a DOS file you'll see a "
"\"^M\" (control m is carriage return) at the end of each line. And that is "
"why scripts don't work when written with Microsoft Notepad. The kernel looks "
"for \"/bin/sh^M\" which doesn't exist. There's a \"/bin/sh\", but nothing "
"with a \"^M\" appended."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:325
msgid ""
"MacOs: CR only. Printers probably print every line atop the first, and Unix "
"tools think the whole file is one line with \"^M\" all through it."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:329
msgid "To change DOS to Unix, use"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:331
msgid "cp &lt;fileid&gt; &lt;fileid&gt;.dos &amp;&amp;"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:332
msgid "cat &lt;fileid&gt;.dos | tr -d '\\r' &gt; &lt;fileid&gt;"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:334
msgid ""
"Or in <code>vim</code>, you can convert a file with <code>:set ff={unix, "
"dos, mac}</code>. Other conversions will probably require sed or a different "
"use of tr and are left as an exercise for the reader."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:341
msgid "Is there a way to download all current files at one time?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:343
msgid ""
"Yes. You can download the file LFS-BOOK-x.y-wget-list <a href= "
"\"http://www.linuxfromscratch.org/lfs/downloads/stable\"> "
"http://www.linuxfromscratch.org/lfs/downloads/stable</a>. To download all "
"the files, use the version of <code>wget</code> on your host distribution to "
"run:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:348
msgid "<code>wget --input-file=LFS-BOOK-x.y-wget-list</code>"
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:354
msgid "General compilation errors"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:356
msgid "I used a patch from GNU to upgrade. Is that OK?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:358
msgid ""
"Patches from GNU don't usually work. You can either download the full "
"archive and try again or try the solution given by Gerard Beekmans:"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:361
msgid ""
"The problem is that executable marked scripts are patched too and they then "
"lose the executable bit, so you can't execute those scripts anymore until "
"you run a \"chmod +x\" on them (or something similar, like chmod 755) before "
"installing Glibc. Try chmod +x glibc-2.2.5/scripts/* (not 100% sure about "
"the directory paths but it should be obvious where to do it when running an "
"'ls' on the glibc-2.2.5 directory)."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:369
msgid "When using optimization flags (setting CFLAGS)"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:371
msgid ""
"If you're getting errors and you're setting CFLAGS or otherwise passing "
"optimization flags to the compiler that may be the problem."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:374
msgid ""
"If you ask on the list and they can't figure it out immediately, they'll "
"likely suggest trying it without optimization. So if you just retry it "
"without before asking, you'll be one step ahead of them :)"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:378
msgid ""
"Of particular note is that optimizing binutils, gcc, or glibc may cause any "
"other package to fail to compile or run or to otherwise misbehave in strange "
"and mysterious ways. Also, optimization that works for someone else may not "
"work for you. Flags that used to work may mysteriously stop working. Even "
"some small innocent hardware change can make the difference."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:384
msgid ""
"(If you don't know what optimization flags are, don't worry, you really "
"don't need to.)"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:386
msgid "Why does configure hang at \"checking for signed size_t type...\"?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:388
msgid "You over optimized gcc."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:390
msgid "I didn't delete the source tree after my last attempt. Do I need to?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:392
msgid ""
"Yes. In general <code>make clean</code> or <code>make dist-clean</code> "
"can't be relied upon for clean sources. Especially when you have manually "
"hacked the sources or applied patches to it you should first try again with "
"a fresh unpacked package. The only exception to this rule is the linux "
"kernel, which requires its sources to be present when third-party modules, "
"such as the NVidia drivers, are needed."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:400
msgid "I'm getting `/dev/null: Permission denied'"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:402
msgid "Does /dev/null look like this:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:404
msgid "$ ls -l /dev/null"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:405
msgid "crw-rw-rw- 1 root root 1, 3 Aug 3 2000 /dev/null"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:407
msgid ""
"If not, it should. See the chmod(1), chown(1), and mknod(1) man pages and "
"/usr/src/linux/Documentation/devices.txt if you need help fixing it."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:410
msgid ""
"If it does look right, the problem is probably your mount options.  See the "
"answer to \"<a href=\"#bad-interpreter-permission-denied\">./configure: bad "
"interpreter: Permission denied</a>\", above."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:415
msgid "signal 11 (internal error: Segmentation fault)"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:417
msgid ""
"The long answer is at <a "
"href=\"http://www.bitwizard.nl/sig11/\">http://www.bitwizard.nl/sig11/</a>."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:419
msgid ""
"The short answer is that if restarting make gets a little further every "
"time, you have a hardware problem. (If make, or whatever you're running, "
"fails at the same place every time, then it is not hardware.)"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:423
msgid ""
"Assuming you're not overclocking, the most likely hardware problem is bad "
"memory which you can check with Memtest86 from <a "
"href=\"http://www.memtest86.com/\">http://www.memtest86.com/</a>. If that "
"isn't it, see the long answer."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:428
msgid "No such file or directory"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:430
msgid "Examples of this error are:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:432
msgid "/usr/bin/env: /tools/bin/bash: No such file or directory"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:433
msgid "gcc: No such file or directory"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:435
msgid ""
"This usually indicates a typo in the GCC Pass 2 installation. For older LFS "
"versions, the most common cause of this problem would be forgetting to apply "
"the specs patch."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:438
msgid ""
"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."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:443
msgid ""
"You can test this with <code>readelf -l {binary} | grep "
"interpreter</code>. Its output should be: <code>Requesting program "
"interpreter: /tools/lib/ld-linux.so.2</code>."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:447
msgid "bash: ./configure: No such file or directory"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:449
msgid ""
"You forgot to <code>cd</code> into the extracted directory of the package "
"after you've extracted it."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:451
msgid "./configure: bad interpreter: Permission denied"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:453
msgid ""
"You're most likely getting this while building binutils in Chapter 5 of the "
"LFS Book. The problem is most likely your mount options. You probably have a "
"line in /etc/fstab like:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:456
msgid "<code>/dev/hda10 /mnt/lfs ext2 user 1 2</code>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:457
msgid ""
"'user' is the mount flag, and it's the problem. To quote from the mount man "
"page:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:458
msgid ""
"<cite>user: Allow an ordinary user to mount the file system. This option "
"implies the options noexec, nosuid, and nodev (unless overridden by "
"subsequent options, as in the option line user,exec,dev,suid).</cite>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:462
msgid "So change the line in /etc/fstab like this:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:463
msgid "<code>/dev/hda10 /mnt/lfs ext2 defaults 1 2</code>"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:465
msgid "configure can't guess my host type."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:467
msgid "Typical symptoms look like this:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:469
msgid "sk ~/tmp-0.0 $ ./configure"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:470
msgid "creating cache ./config.cache"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:471
msgid "checking host system type..."
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:472
msgid ""
"<strong>configure: error: can not guess host type; you must specify "
"one</strong>"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:473
msgid "sk ~/tmp-0.0 $"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:475
msgid ""
"The problem is usually that the script can't run the compiler.  Usually it's "
"just a missing /usr/bin/cc symlink. You can fix it like this:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:478
msgid "<code>cd /usr/bin &amp;&amp; ln -s gcc cc</code>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:479
msgid ""
"If that doesn't do it, check the file config.log created by "
"configure. Errors are recorded there and may indicate the problem."
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:483 faq-en.html:487
msgid "checking whether we are using GNU C... no"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:485
msgid "If you're getting an error from configure like:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:488
msgid "configure: error: GNU libc must be compiled using GNU CC"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:490
msgid ""
"It may be because egrep isn't working. Since egrep is a shell-script which "
"calls grep, this actually means there's a problem with grep."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:493
msgid ""
"To test if grep is working <em>before</em> reinstalling the grep package in "
"Chapter 6, run the following command from <em>outside</em> chroot:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:496
msgid "<code>file $LFS/bin/grep</code>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:497
msgid ""
"If it doesn't say <code>statically linked</code> you have a problem and need "
"to reinstall the grep package according to the instruction in chapter 5."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:500
msgid ""
"To test if egrep is working <em>after</em> reinstalling the grep package in "
"Chapter 6, run the following command from <em>inside</em> chroot:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:503
msgid "<code>egrep root /etc/passwd</code>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:504
msgid ""
"If it doesn't print root's line from /etc/passwd, again, you have a "
"problem. (This test also works if you encounter the problem after rebooting "
"into the new LFS system.)"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:508
msgid "The system has no more ptys.  Ask your system administrator to create more."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:511
msgid "If you run"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:513
msgid "expect -c &quot;spawn ls&quot;"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:515
msgid "and get the following error:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:517
msgid "The system has no more ptys."
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:518
msgid "Ask your system administrator to create more."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:520
msgid ""
"then your linux distribution is either not setup to use Unix98 PTYs or to "
"use the /dev/pts file system."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:522
msgid ""
"The solution may require recompiling your kernel. First, go to your kernel's "
"source directory and look at the .config file. If you do not have a .config "
"file, and you are running the pre-compiled kernel that was installed with "
"rpm, aptget, or whatever your distribution uses, then you need to seek "
"support from your distribution's support FAQ's, mailing lists or IRC "
"channels."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:528
msgid "If you do have a .config file, look inside it for the following 2 options:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:530
msgid "CONFIG_UNIX98_PTYS=y"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:531
msgid "CONFIG_DEVPTS_FS=y"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:533
msgid ""
"If either of these has 'n' instead of 'y', then change it and recompile the "
"kernel."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:534
msgid ""
"If they both have 'y', then you probably will not have to recompile the "
"kernel."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:535
msgid ""
"Next, we need to ensure that the system is actually using both Unix98 PTYs "
"and the /dev/pts file system."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:537
msgid ""
"First, look for a device called /dev/ptmx.  If it doesn't exist, create it "
"with:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:539
msgid "mknod /dev/ptmx c 5 2"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:541
msgid "Then, whether it existed or you just created it, run:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:543
msgid "chmod 666 /dev/ptmx"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:545
msgid ""
"Next, ensure that there is a directory called /dev/pts.  The permissions "
"should be 755.  Create it and/or chmod it if needed."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:547
msgid "The final setup is to add the following line to /etc/fstab:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:549
msgid "devpts&nbsp;&nbsp;&nbsp;&nbsp;/dev/pts&nbsp;&nbsp;&nbsp;&nbsp;devpts&nbsp;&nbsp;&nbsp;&nbsp;gid=5,mode=620&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;0"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:551
msgid ""
"NOTE: Look for the tty group in /etc/group and note the group id number.  "
"Change the gid=5 option to match the group id number of the tty group.  The "
"group id of 5 is just an example and may differ on your system."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:555
msgid "Now that everything is setup, you have two options."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:556
msgid "1.  Mount /dev/pts and test it by rerunning the above expect command."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:557
msgid "2.  Reboot the computer and test it by rerunning the above expect command."
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:562
msgid "Package-specific errors"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:564
msgid "GCC: Error: Unknown pseudo-op: `.hidden'"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:566
msgid "If compiling GCC in Chapter 5 errors out with"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:567
msgid "<code>Error: Unknown pseudo-op: `.hidden'</code>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:568
msgid ""
"Try the solution given in <a "
"href=\"http://linuxfromscratch.org/pipermail/lfs-support/2002-September/009562.html\">the "
"lfs-support archives</a> and replies."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:572
msgid "Glibc fails and mentions BEGIN and END."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:574
msgid "If glibc fails to build with an error like this:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:576
msgid "'BEGIN { subdirs = \"\"; inhibit = \"\" }; \\"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:577
msgid "^# { next }; \\"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:578
msgid "^[^-] { subdirs = subdirs \" \" $0 }; \\"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:579
msgid "^- { inhibit = inhibit \" \" substr($0, 2) }; \\"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:580
msgid "END { printf \"sysdep-subdirs =%s\\n\", subdirs; \\"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:581
msgid "printf \"sysdep-inhibit-subdirs =%s\\n\", inhibit; \\"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:582
msgid "print \"sysd-dirs-done = t\" }' \\"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:583
msgid "/dev/null linuxthreads/sysdeps/pthread/Subdirs"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:584
msgid "sysdeps/unix/inet/Subdirs sysdeps/unix/Subdirs &gt;"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:585
msgid "/usr/src/glibc-build/sysd-dirs-tmp"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:586
msgid "/bin/sh: line 1: BEGIN { subdirs = \"\"; inhibit = \"\" };"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:587
msgid "^# { next };"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:588
msgid "^[^-] { subdirs = subdirs \" \" $0 }; ^- { inhibit ="
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:589
msgid "inhibit \" \" substr($0, 2) }; END"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:591
msgid ""
"then gawk is failing. The key is the BEGIN and END in the output.  The "
"probable reason is that it is linked incorrectly. This can be fixed by "
"recompiling it as the lfs user, according to the directions in Chapter 5."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:596
msgid "Glibc compilation errors out due to a missing nss.h header file"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:598
msgid ""
"This usually indicates that you are compiling LFS onto a Reiser4 "
"partition. Unfortunately, there is currently no known solution, other than "
"to use a different type of filesystem."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:602
msgid "NCurses: C++ preprocessor &quot;/lib/cpp&quot; fails sanity check"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:604
msgid "Ncurses in chapter six ends with:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:606
msgid "checking how to run the C++ preprocessor... /lib/cpp"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:607
msgid "configure: error: C++ preprocessor \"/lib/cpp\" fails sanity check"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:609
msgid ""
"The problem is that you have no c++ compiler. In chapter five, gcc is first "
"built without the C++ compiler. Before building ncurses, gcc is rebuilt with "
"the C++ compiler. Most probably, you forgot to extract the g++ tarball, or "
"did not specify \"c++\" in the --enable-languages configure switch, on the "
"2nd gcc build. There are more details in <a "
"href=\"http://archives.linuxfromscratch.org/mail-archives/lfs-support/2003-July/018757.html\">the "
"mail archive</a>."
msgstr ""

#. type: Content of: <h3>
#: faq-en.html:621
msgid "Configuration and booting issues"
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:623
msgid "Kernel panic: VFS: unable to mount root fs"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:625
msgid ""
"There are several reasons why the kernel might be unable to mount the root "
"filesystem."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:627
msgid "Did you specify the correct partition in <code>/boot/grub/menu.lst</code>?"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:629
msgid ""
"Is support for the hard drive enabled in the kernel. For SCSI this means "
"support for the specific SCSI adapter."
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:631
msgid ""
"Is support for the hard drive compiled into the kernel, not just as a "
"module. (Modules are stored on the filesystem. If a driver needed to access "
"the filesystem is stored as a module on that filesystem, well ... you know "
"... ;)"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:635
msgid ""
"Is support for the filesystem compiled into the kernel. Again, not a "
"module. Support for ext2 is enabled by default, but others like ext3, "
"reiser, jfs, and xfs are not."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:640
msgid "init: Id \"1\" respawning too fast: disabled for 5 minutes"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:642
msgid "When you see, in your syslogs, this line:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:643
msgid "<code>init: Id \"1\" respawning too fast: disabled for 5 minutes</code>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:644
msgid ""
"It means you have an error in the /etc/inittab line beginning with the given "
"id (\"1\" in this example)."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:646
msgid "modprobe: Can't locate module char-major-10-135"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:648
msgid ""
"<code>char-major-10-135</code> refers to the character device, major 10, "
"minor 135, which is /dev/rtc. It provides access to the BIOS clock, or RTC, "
"the Real Time Clock. See /usr/src/linux/Documentation/rtc.txt for more "
"information."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:652
msgid ""
"The error is because something, most likely hwclock, is trying to use "
"/dev/rtc but you haven't configured kernel support for it in your "
"kernel. Either delete /dev/rtc so hwclock won't try to use it or enable RTC "
"support in your kernel. It's located in make menuconfig under \"Character "
"devices\" -&gt; \"Enhanced Real Time Clock Support\"."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:659
msgid "modprobe: Can't locate module /dev/rtc"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:661
msgid ""
"See the question <a href=\"#char-major-10-135\">\"modprobe: Can't locate "
"module char-major-10-135\"</a>."
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:663 faq-en.html:667
msgid "eth0:unknown interface:No such device [failed]"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:665
msgid "The full error looks like this:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:668
msgid "Setting up default gateway..."
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:669
msgid "SIOCADDRT:No such device [failed]"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:671
msgid ""
"eth0 is a virtual device with no /dev entry. It refers to the first detected "
"network card in your system. The reason the kernel can't find this device is "
"because you forgot to add support for your network card in the kernel. The "
"kernel detected the card but doesn't have a driver for it. The LFS boot "
"script tries to bring up the network but fails because of this."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:677
msgid ""
"Recompile your kernel with the proper driver, either built in or as a "
"module. If you compiled the network driver as a module, then also adjust "
"/etc/modules.conf to alias the network card module as eth0; for example: "
"<code>alias eth0 8139too</code>. If you don't know which network card you "
"have, you can use <code>dmesg</code>, /proc/pci or <code>lspci</code> to "
"find out."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:684
msgid "spurious 8259A interrupt: IRQ14"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:686
msgid ""
"Short summary: It's a hardware problem (usually). Transient "
"Line-noise/crosstalk persuades the PIC that something happened; this can "
"result in a 'dummy' interrupt being raised, which happens to be IRQ7 with "
"intel's 8259 design.The problem could possibly also be caused by (or instead "
"be caused by) a device driver not properly masking its interrupts before "
"servicing, this would be the suspect if the IRQ7's were happening in bursts, "
"or more often than 'several' per day. (<a "
"href=\"http://groups.google.com/groups?q=spurious+interrupt+8259&amp;hl=de&amp;scoring=d&amp;selm=3C174EDD.9090306%40hotmail.com&amp;rnum=10\">Source "
"and additional information</a>)"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:696
msgid ""
"Since the message itself is harmless, it's enough to adjust the default "
"loglevel outplut of klogd (the -c opion) in the syslogd bootscript. See "
"<code>man klogd</code> for details. You can also try recompiling the kernel "
"and unset CONFIG_LOCAL_APIC."
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:701
msgid "Why does less (and therefore man) print &lt;AD&gt; instead of hyphens?"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:703
msgid ""
"Because the LANG and LC_ALL environment variables aren't set. To fix that, "
"set them in both the ~/.bash_profile and ~/.bashrc files for each user or in "
"/etc/profile, which will take care of all users, by adding lines like this:"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:708
msgid "export LANG=en_US"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:709
msgid "export LC_ALL=POSIX"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:711
msgid "Those lines can be added to /etc/profile with the following command:"
msgstr ""

#. type: Content of: <dl><dd>
#: faq-en.html:712
msgid ""
"<code>echo -e 'export LANG=en_US\\nexport LC_ALL=POSIX' &gt;&gt; "
"/etc/profile</code>"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:713
msgid ""
"If you don't use US English you'll have to change the \"en_US\" part and "
"possibly the values of various LC_* variables as well. Running the locale "
"command lists many (all?) of the LC_* variables."
msgstr ""