lfs-book-i18n/zh_CN/chapter04/creatingtoolsdir.po

# 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: 2020-06-17 12:44+0800\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=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. type: Content of: <sect1><title>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:11
msgid "Creating the $LFS/tools Directory"
msgstr ""

#. type: Content of: <sect1><para>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:13
msgid ""
"All programs compiled in <xref linkend=\"chapter-temporary-tools\"/> will be "
"installed under <filename class=\"directory\">$LFS/tools</filename> to keep "
"them separate from the programs compiled in <xref "
"linkend=\"chapter-building-system\"/>. The programs compiled here are "
"temporary tools and will not be a part of the final LFS system. By keeping "
"these programs in a separate directory, they can easily be discarded later "
"after their use. This also prevents these programs from ending up in the "
"host production directories (easy to do by accident in <xref "
"linkend=\"chapter-temporary-tools\"/>)."
msgstr ""

#. type: Content of: <sect1><para>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:23
msgid ""
"Create the required directory by running the following as <systemitem "
"class=\"username\">root</systemitem>:"
msgstr ""

#. type: Content of: <sect1><screen>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:26
#, no-wrap
msgid "<userinput>mkdir -v $LFS/tools</userinput>"
msgstr ""

#. type: Content of: <sect1><para>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:28
msgid ""
"The next step is to create a <filename class=\"symlink\">/tools</filename> "
"symlink on the host system. This will point to the newly-created directory "
"on the LFS partition. Run this command as <systemitem "
"class=\"username\">root</systemitem> as well:"
msgstr ""

#. type: Content of: <sect1><screen>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:33
#, no-wrap
msgid "<userinput>ln -sv $LFS/tools /</userinput>"
msgstr ""

#. type: Content of: <sect1><note><para>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:36
msgid ""
"The above command is correct. The <command>ln</command> command has a few "
"syntactic variations, so be sure to check <command>info coreutils "
"ln</command> and <filename>ln(1)</filename> before reporting what you may "
"think is an error."
msgstr ""

#. type: Content of: <sect1><para>
#: /home/xry111/svn-repos/LFS-BOOK/chapter04/creatingtoolsdir.xml:42
msgid ""
"The created symlink enables the toolchain to be compiled so that it always "
"refers to <filename class=\"directory\">/tools</filename>, meaning that the "
"compiler, assembler, and linker will work both in Chapter&nbsp;5 (when we "
"are still using some tools from the host) and in the next (when we are "
"<quote>chrooted</quote> to the LFS partition)."
msgstr ""