Subversion Repositories svn LFS-FR

Rev

Rev 7248 | 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.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2017-03-12 09:47+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"

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

#. type: Content of: <p>
#: faq-en.html:3
#, no-wrap
msgid "The FAQ is divided in three documents. The "
msgstr ""

#. type: Content of: <p><a>
#: faq-en.html:4
#, no-wrap
msgid "General FAQ"
msgstr ""

#. type: Content of: <p>
#: faq-en.html:4
#, no-wrap
msgid ""
" has links to all questions and\n"
"      answers. The "
msgstr ""

#. type: Content of: <p><a>
#: faq-en.html:5
#, no-wrap
msgid "LFS FAQ"
msgstr ""

#. type: Content of: <p>
#: faq-en.html:5
#, no-wrap
msgid ""
" is a selection of\n"
"      LFS-specific FAQ's and the "
msgstr ""

#. type: Content of: <p><a>
#: faq-en.html:6
#, no-wrap
msgid "BLFS FAQ"
msgstr ""

#. type: Content of: <p>
#: faq-en.html:6
#, no-wrap
msgid ""
" is a\n"
"      selection of BLFS-specific FAQ's."
msgstr ""

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

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

#. type: Content of: <ul><li><a>
#: faq-en.html:12
#, no-wrap
msgid "Why not upgrade LILO to the latest version?"
msgstr ""

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

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

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

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

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

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

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

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

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

#. type: Content of: <ul><li><a>
#: faq-en.html:24
#, no-wrap
msgid "Do I need to keep the source after installing?"
msgstr ""

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#. type: Content of: <ul><li><a>
#: faq-en.html:59
#, no-wrap
msgid "eth0:unknown interface"
msgstr ""

#. type: Content of: <ul><li><a>
#: faq-en.html:60
#, no-wrap
msgid "spurious 8259A interrupt: IRQ14"
msgstr ""

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:89
#, no-wrap
msgid "This is fairly well discussed in the thread starting at "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:90
#, no-wrap
msgid "http://linuxfromscratch.org/pipermail/lfs-dev/2002-February/023030.html"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:90 faq-en.html:172 faq-en.html:173 faq-en.html:174 faq-en.html:176 faq-en.html:181 faq-en.html:185 faq-en.html:188 faq-en.html:191 faq-en.html:193 faq-en.html:234 faq-en.html:242 faq-en.html:291 faq-en.html:304 faq-en.html:418 faq-en.html:445 faq-en.html:616 faq-en.html:661
#, no-wrap
msgid "."
msgstr ""

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

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

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

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

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

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

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

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

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:110
#, no-wrap
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
#, no-wrap
msgid "Theoretically less stable due to newness of code"
msgstr ""

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

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

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

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:117
#, no-wrap
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
#, no-wrap
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
#, no-wrap
msgid "Theoretically more stable"
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:129
#, no-wrap
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
#, no-wrap
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
#, no-wrap
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
#, no-wrap
msgid "Test like crazy by running the test suites"
msgstr ""

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

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

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

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

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

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

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:165
#, no-wrap
msgid ""
"RPM, the Redhat Package Manager, is used by a number of\n"
"            distributions. It is available from "
msgstr ""

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:167
#, no-wrap
msgid "http://www.rpm.org/"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:167
#, no-wrap
msgid ""
", and there is an\n"
"            "
msgstr ""

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:168
#, no-wrap
msgid "RPM Hint"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:168
#, no-wrap
msgid ""
" to help with\n"
"            installation."
msgstr ""

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

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:172
#, no-wrap
msgid "Epkg is available from "
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li><a>
#: faq-en.html:172
#, no-wrap
msgid "http://www.encap.org/epkg/"
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:173
#, no-wrap
msgid "Graft is available from "
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li><a>
#: faq-en.html:173
#, no-wrap
msgid "http://peters.gormand.com.au/Home/tools"
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:174
#, no-wrap
msgid "GNU Stow is available from "
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li><a>
#: faq-en.html:174
#, no-wrap
msgid "http://www.gnu.org/software/stow/"
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li>
#: faq-en.html:175
#, no-wrap
msgid "And several more are listed in the Graft documentation at "
msgstr ""

#. type: Content of: <dl><dd><ul><li><ul><li><a>
#: faq-en.html:176
#, no-wrap
msgid "http://peters.gormand.com.au/Home/tools/graft/graft-html#research"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:179
#, no-wrap
msgid ""
"The NetBSD package manager, pkgsrc, is available on other\n"
"            systems including Linux. It is at "
msgstr ""

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:181
#, no-wrap
msgid "ftp://ftp.netbsd.org/pub/pkgsrc/stable/"
msgstr ""

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

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:185
#, no-wrap
msgid "http://install-log.sourceforge.net/"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:186
#, no-wrap
msgid ""
"Gerard has since made additions to his script. It is available\n"
"            from "
msgstr ""

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:188
#, no-wrap
msgid "http://linuxfromscratch.org/~gerard/log-install"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:189
#, no-wrap
msgid ""
"CheckInstall attempts log system calls made by \"make install\".\n"
"            It is available from "
msgstr ""

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:191
#, no-wrap
msgid "http://asic-linux.com.mx/~izto/checkinstall/"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:192
#, no-wrap
msgid "pkgutils, used by the CRUX distribution, is available from "
msgstr ""

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:193
#, no-wrap
msgid "http://www.fukt.bsnet.se/~per/pkgutils/"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:194
#, no-wrap
msgid "There are some "
msgstr ""

#. type: Content of: <dl><dd><ul><li><a>
#: faq-en.html:194
#, no-wrap
msgid "hints"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:194
#, no-wrap
msgid " available for package managers."
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:202
#, no-wrap
msgid ""
"Power Management is a kernel function, you need to enable it in\n"
"          the kernel. In the 2.4 kernel, you have to enable the options "
"for\n"
"          "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:204
#, no-wrap
msgid "Power Management Support"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:204
#, no-wrap
msgid " under "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:204
#, no-wrap
msgid ""
"General\n"
"          Setup"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:205
#, no-wrap
msgid ""
". For older machines, you'll probably want the APM\n"
"          options, newer machines often require ACPI. Make sure that either "
"APM\n"
"          or ACPI be enabled in the kernel, but definitely "
msgstr ""

#. type: Content of: <dl><dd><p><strong>
#: faq-en.html:207
#, no-wrap
msgid "not"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:208
#, no-wrap
msgid ""
"          both at the same time - this has been known to cause problems such "
"as\n"
"          neither actually taking effect. Also try disabling SMP if you "
"only\n"
"          have one processor; it's also known to prevent a proper "
"poweroff.\n"
"          Make sure you read the help with each option."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:212
#, no-wrap
msgid ""
"After rebooting into the new kernel you should be able to poweroff\n"
"          your machine with the command "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:213
#, no-wrap
msgid "shutdown -h now"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:213
#, no-wrap
msgid ""
" or\n"
"          "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:214
#, no-wrap
msgid "poweroff"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:214
#, no-wrap
msgid " (also read "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:214
#, no-wrap
msgid "man shutdown"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:214
#, no-wrap
msgid ""
" and\n"
"          "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:215
#, no-wrap
msgid "man halt"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:215
#, no-wrap
msgid ""
"). If you compiled APM or ACPI as modules, make\n"
"          sure they are loaded before you try to power off.  Some machines\n"
"          require that APM or ACPI is compiled into the kernel because it "
"needs\n"
"          to be initialised at boottime. "
msgstr ""

#. type: Content of: <p><a>
#: faq-en.html:221 faq-en.html:352 faq-en.html:560 faq-en.html:619
#, no-wrap
msgid "Back to the top."
msgstr ""

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

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:234
#, no-wrap
msgid "Knoppix"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:238
#, no-wrap
msgid "In addition to the kernel documentation at "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:239
#, no-wrap
msgid "/usr/src/linux/Documentation"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:240
#, no-wrap
msgid ""
"          or wherever you unpacked your kernel source and the help in "
"kernel\n"
"          config tool (make menuconfig), see the Module-HOWTO at "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:242
#, no-wrap
msgid "http://www.tldp.org/HOWTO/Module-HOWTO/"
msgstr ""

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

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

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

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

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

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

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

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

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

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

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

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

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

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:264
#, no-wrap
msgid "               int main() { e"
msgstr ""

#. type: Content of: <dl><dd><div><p><span>
#: faq-en.html:264
#, no-wrap
msgid "xx"
msgstr ""

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:264
#, no-wrap
msgid "it(0) }"
msgstr ""

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:276
#, no-wrap
msgid "Gerard describes the process of making a 5MB LFS install in "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:277
#, no-wrap
msgid ""
"an\n"
"          email to lfs-support"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:278
#, no-wrap
msgid ""
",  and there are links to many resources in\n"
"          "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:280
#, no-wrap
msgid ""
"a\n"
"          post by Cor Lem"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:281
#, no-wrap
msgid " and a reply to it."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:285
#, no-wrap
msgid ""
"For information about building LFS for a wide array of systems,\n"
"          take a look at the "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:287
#, no-wrap
msgid "Cross-LFS branch"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:287
#, no-wrap
msgid ""
" of\n"
"          LFS."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:289
#, no-wrap
msgid ""
"For Alpha systems, Kelledin maintains a list of fixes for building\n"
"          on the Alpha platform at "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:291
#, no-wrap
msgid "http://skarpsey.dyndns.org/alpha-lfs/alpha.html"
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:301
#, no-wrap
msgid "The LFS book specifically for cross compiling is the "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:302
#, no-wrap
msgid "Cross-LFS"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:302
#, no-wrap
msgid ""
" book.\n"
"          Another source of information would be the "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:304
#, no-wrap
msgid "cross-compiling hint"
msgstr ""

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

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

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:311
#, no-wrap
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
#, no-wrap
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
#, no-wrap
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
#, no-wrap
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
#, no-wrap
msgid "                &nbsp;&nbsp;like"
msgstr ""

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

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

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:334
#, no-wrap
msgid "Or in "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:334
#, no-wrap
msgid "vim"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:334
#, no-wrap
msgid ", you can convert a file with "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:334
#, no-wrap
msgid ""
":set\n"
"          ff={unix, dos, mac}"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:335
#, no-wrap
msgid ""
". Other conversions will probably require\n"
"          sed or a different use of tr and are left as an exercise for the\n"
"          reader."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:343
#, no-wrap
msgid "Yes. You can download the file LFS-BOOK-x.y-wget-list "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:345
#, no-wrap
msgid "          http://www.linuxfromscratch.org/lfs/downloads/stable"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:345
#, no-wrap
msgid ""
". To download all the files,\n"
"          use the version of "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:346
#, no-wrap
msgid "wget"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:346
#, no-wrap
msgid " on your host distribution to run:"
msgstr ""

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

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:384
#, no-wrap
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
#, no-wrap
msgid "Why does configure hang at \"checking for signed size_t type...\"?"
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:392
#, no-wrap
msgid "Yes. In general "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:392
#, no-wrap
msgid "make clean"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:392
#, no-wrap
msgid " or "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:392
#, no-wrap
msgid ""
"make\n"
"          dist-clean"
msgstr ""

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

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

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

#. type: Content of: <dl><dd><div><p>
#: faq-en.html:405
#, no-wrap
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
#, no-wrap
msgid ""
"If not, it should. See the chmod(1), chown(1), and mknod(1) man\n"
"          pages and /usr/src/linux/Documentation/devices.txt if you need "
"help\n"
"          fixing it."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:410
#, no-wrap
msgid ""
"If it does look right, the problem is probably your mount options.\n"
"          See the answer to \""
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:412
#, no-wrap
msgid ""
"./configure: bad\n"
"          interpreter: Permission denied"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:413
#, no-wrap
msgid "\", above."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:417
#, no-wrap
msgid "The long answer is at "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:418
#, no-wrap
msgid "http://www.bitwizard.nl/sig11/"
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:423
#, no-wrap
msgid ""
"Assuming you're not overclocking, the most likely hardware problem\n"
"          is bad memory which you can check with Memtest86 from "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:425
#, no-wrap
msgid "http://www.memtest86.com/"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:425
#, no-wrap
msgid ""
". If\n"
"          that isn't it, see the long answer."
msgstr ""

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:438
#, no-wrap
msgid ""
"What happens is that the path to the dynamic linker embedded\n"
"          inside the executable is still pointing at /lib/ld-linux.so.2 "
"and\n"
"          when one goes to run the binary inside the chroot where\n"
"          /lib/ld-linux.so.2 does not exist yet, the very unhelpful "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:441
#, no-wrap
msgid ""
"No\n"
"          such file or directory"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:442
#, no-wrap
msgid " error message is shown."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:443
#, no-wrap
msgid "You can test this with "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:443
#, no-wrap
msgid ""
"readelf -l {binary} | grep\n"
"          interpreter"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:444
#, no-wrap
msgid ". Its output should be: "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:444
#, no-wrap
msgid ""
"Requesting program\n"
"          interpreter: /tools/lib/ld-linux.so.2"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:449
#, no-wrap
msgid "You forgot to "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:449
#, no-wrap
msgid "cd"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:449
#, no-wrap
msgid " into the extracted directory of the package after you've extracted it."
msgstr ""

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:493
#, no-wrap
msgid "To test if grep is working "
msgstr ""

#. type: Content of: <dl><dd><p><em>
#: faq-en.html:493
#, no-wrap
msgid "before"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:493 faq-en.html:500
#, no-wrap
msgid ""
" reinstalling the grep\n"
"          package in Chapter 6, run the following command from "
msgstr ""

#. type: Content of: <dl><dd><p><em>
#: faq-en.html:494
#, no-wrap
msgid "outside"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:495 faq-en.html:502
#, no-wrap
msgid "          chroot:"
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:497
#, no-wrap
msgid "If it doesn't say "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:497
#, no-wrap
msgid "statically linked"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:497
#, no-wrap
msgid ""
" you have a\n"
"          problem and need to reinstall the grep package according to the\n"
"          instruction in chapter 5."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:500
#, no-wrap
msgid "To test if egrep is working "
msgstr ""

#. type: Content of: <dl><dd><p><em>
#: faq-en.html:500
#, no-wrap
msgid "after"
msgstr ""

#. type: Content of: <dl><dd><p><em>
#: faq-en.html:501
#, no-wrap
msgid "inside"
msgstr ""

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

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

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

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

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

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:528
#, no-wrap
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
#, no-wrap
msgid "CONFIG_UNIX98_PTYS=y"
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:533
#, no-wrap
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
#, no-wrap
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
#, no-wrap
msgid ""
"Next, we need to ensure that the system is actually using both\n"
"          Unix98 PTYs and the /dev/pts file system."
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:537
#, no-wrap
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
#, no-wrap
msgid "mknod /dev/ptmx c 5 2"
msgstr ""

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:556
#, no-wrap
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
#, no-wrap
msgid "2.  Reboot the computer and test it by rerunning the above expect command."
msgstr ""

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:568
#, no-wrap
msgid "Try the solution given in "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:569
#, no-wrap
msgid ""
"the\n"
"          lfs-support archives"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:570
#, no-wrap
msgid "  and replies."
msgstr ""

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:615
#, no-wrap
msgid ""
"the\n"
"          mail archive"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:625
#, no-wrap
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
#, no-wrap
msgid ""
"Did you specify the correct partition in\n"
"            "
msgstr ""

#. type: Content of: <dl><dd><ul><li><code>
#: faq-en.html:628
#, no-wrap
msgid "/boot/grub/menu.lst"
msgstr ""

#. type: Content of: <dl><dd><ul><li>
#: faq-en.html:628
#, no-wrap
msgid "?"
msgstr ""

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:644
#, no-wrap
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><dd><p><code>
#: faq-en.html:648
#, no-wrap
msgid "char-major-10-135"
msgstr ""

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:661
#, no-wrap
msgid "See the question "
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:661
#, no-wrap
msgid "\"modprobe: Can't locate module char-major-10-135\""
msgstr ""

#. type: Content of: <dl><dt>
#: faq-en.html:663
#, no-wrap
msgid "eth0:unknown interface:No such device [failed] "
msgstr ""

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:677
#, no-wrap
msgid ""
"Recompile your kernel with the proper driver, either built in or\n"
"          as a module. If you compiled the network driver as a module, "
"then\n"
"          also adjust /etc/modules.conf to alias the network card module "
"as\n"
"          eth0; for example: "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:680
#, no-wrap
msgid "alias eth0 8139too"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:680
#, no-wrap
msgid ""
". If you don't know\n"
"          which network card you have, you can use "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:681
#, no-wrap
msgid "dmesg"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:681
#, no-wrap
msgid ""
",\n"
"          /proc/pci or "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:682
#, no-wrap
msgid "lspci"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:682
#, no-wrap
msgid " to find out."
msgstr ""

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:686
#, no-wrap
msgid ""
"Short summary: It's a hardware problem (usually). Transient\n"
"          Line-noise/crosstalk persuades the PIC that something happened; "
"this\n"
"          can result in a 'dummy' interrupt being raised, which happens to "
"be\n"
"          IRQ7 with intel's 8259 design.The problem could possibly also be\n"
"          caused by (or instead be caused by) a device driver not properly\n"
"          masking its interrupts before servicing, this would be the suspect "
"if\n"
"          the IRQ7's were happening in bursts, or more often than 'several' "
"per\n"
"          day. ("
msgstr ""

#. type: Content of: <dl><dd><p><a>
#: faq-en.html:694
#, no-wrap
msgid ""
"Source\n"
"          and additional information"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:695
#, no-wrap
msgid ")"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:696
#, no-wrap
msgid ""
"Since the message itself is harmless, it's enough to adjust the\n"
"          default loglevel outplut of klogd (the -c opion) in the syslogd\n"
"          bootscript. See "
msgstr ""

#. type: Content of: <dl><dd><p><code>
#: faq-en.html:698
#, no-wrap
msgid "man klogd"
msgstr ""

#. type: Content of: <dl><dd><p>
#: faq-en.html:698
#, no-wrap
msgid ""
" for details. You can also try\n"
"          recompiling the kernel and unset CONFIG_LOCAL_APIC."
msgstr ""

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

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

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

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

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

#. type: Content of: <dl><dd><p>
#: faq-en.html:713
#, no-wrap
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 ""