Fix a couple of typos

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10234 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Matthew Burgess 2013-03-30 09:08:21 +00:00
parent 6458e3172e
commit 395cf94ffb
4 changed files with 14 additions and 14 deletions

View File

@ -52,6 +52,12 @@
linker and assembler to determine which of their own features to linker and assembler to determine which of their own features to
enable.</para> enable.</para>
<para>Fix a couple of syntax errors that prevent the documentation from
building with Texinfo-&texinfo-version;:</para>
<screen><userinput remap="pre">sed -i -e 's/@colophon/@@colophon/' \
-e 's/doc@cygnus.com/doc@@cygnus.com/' bfd/doc/bfd.texinfo</userinput></screen>
<para>The Binutils documentation recommends building Binutils outside of the <para>The Binutils documentation recommends building Binutils outside of the
source directory in a dedicated build directory:</para> source directory in a dedicated build directory:</para>
@ -70,12 +76,6 @@ cd ../binutils-build</userinput></screen>
<note><para>The approximate build SBU values and required disk space <note><para>The approximate build SBU values and required disk space
in Chapter 5 does not include test suite data.</para></note> in Chapter 5 does not include test suite data.</para></note>
<para>Fix a couple of syntax errors that prevent the documentation from
building with Texinfo-&texinfo-version;:</para>
<screen><userinput remap="pre">sed -i -e 's/@colophon/@@colophon/' \
-e 's/doc@cygnus.com/doc@@cygnus.com/' bfd/doc/bfd.texinfo</userinput></screen>
<para>Now prepare Binutils for compilation:</para> <para>Now prepare Binutils for compilation:</para>
<screen><userinput remap="configure">../binutils-&binutils-version;/configure \ <screen><userinput remap="configure">../binutils-&binutils-version;/configure \

View File

@ -43,17 +43,17 @@
<sect2 role="installation"> <sect2 role="installation">
<title>Installation of Binutils</title> <title>Installation of Binutils</title>
<para>Create a separate build directory again:</para>
<screen><userinput remap="pre">mkdir -v ../binutils-build
cd ../binutils-build</userinput></screen>
<para>Fix a couple of syntax errors that prevent the documentation from <para>Fix a couple of syntax errors that prevent the documentation from
building with Texinfo-&texinfo-version;:</para> building with Texinfo-&texinfo-version;:</para>
<screen><userinput remap="pre">sed -i -e 's/@colophon/@@colophon/' \ <screen><userinput remap="pre">sed -i -e 's/@colophon/@@colophon/' \
-e 's/doc@cygnus.com/doc@@cygnus.com/' bfd/doc/bfd.texinfo</userinput></screen> -e 's/doc@cygnus.com/doc@@cygnus.com/' bfd/doc/bfd.texinfo</userinput></screen>
<para>Create a separate build directory again:</para>
<screen><userinput remap="pre">mkdir -v ../binutils-build
cd ../binutils-build</userinput></screen>
<para>Prepare Binutils for compilation:</para> <para>Prepare Binutils for compilation:</para>
<screen><userinput remap="configure">CC=$LFS_TGT-gcc \ <screen><userinput remap="configure">CC=$LFS_TGT-gcc \

View File

@ -32,7 +32,7 @@ ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld</userinput></screen>
<screen><userinput>gcc -dumpspecs | sed -e 's@/tools@@g' \ <screen><userinput>gcc -dumpspecs | sed -e 's@/tools@@g' \
-e '/\*startfile_prefix_spec:/{n;s@.*@/usr/lib/ @}' \ -e '/\*startfile_prefix_spec:/{n;s@.*@/usr/lib/ @}' \
-e '/\*cpp:/{n;s@$@ -isystem /usr/include@}' &amp; \ -e '/\*cpp:/{n;s@$@ -isystem /usr/include@}' &gt; \
`dirname $(gcc --print-libgcc-file-name)`/specs</userinput></screen> `dirname $(gcc --print-libgcc-file-name)`/specs</userinput></screen>
<para>It is a good idea to visually inspect the specs file to verify the <para>It is a good idea to visually inspect the specs file to verify the

View File

@ -1,5 +1,5 @@
<!ENTITY version "SVN-20130329"> <!ENTITY version "SVN-20130330">
<!ENTITY releasedate "March 29, 2013"> <!ENTITY releasedate "March 30, 2013">
<!ENTITY copyrightdate "1999-2013"><!-- jhalfs needs a literal dash, not &ndash; --> <!ENTITY copyrightdate "1999-2013"><!-- jhalfs needs a literal dash, not &ndash; -->
<!ENTITY milestone "7.4"> <!ENTITY milestone "7.4">
<!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" --> <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->