Ken Moffat wrote:
On Sat, Feb 23, 2013 at 11:24:54AM -0600, Bruce Dubbs wrote:
Ken Moffat wrote:

   Cheers, I've just been preparing one (without the three ChangeLog
parts).  Attached.

I don't think that's enough.  The first failure is in
gcc/doc/cppopts.texi and the second failure indicates problems in:


../../gcc-4.7.2/gcc/doc/gcc.texi
../../gcc-4.7.2/gcc/doc/invoke.texi
../../gcc-4.7.2/gcc/doc/extend.texi
../../gcc-4.7.2/gcc/doc/trouble.texi

They all show up as warnings, but that's enough to break the build.

Some of the warnings are easy to fix, but some like the following will
need some research.

../../gcc-4.7.2/gcc/doc/invoke.texi:1017: warning: node next `Overall
Options' in menu `C Dialect Options' and in sectioning `Invoking G++' differ

It turns out that the above warning does not actually stop the build like s/item/itemx/ does.

  Leave it with me - even if a larger patch does solve everything, I
guess a workaround will still be needed in chapter 5 for building
from recent hosts (not just Arch, but also 7.3 building itself or
building next month's svn).

Attached is the diff I got by hacking the .texi files at each error and re-running make. I then extracted the source tarball again and did a diff and edited out the non-applicable files from the actual build. If you do the same for testing, be sure to remove the mpfr, mpc, and gmp directories.

The diff applies to:

patching file gcc/doc/cppopts.texi
patching file gcc/doc/gcc.texi
patching file gcc/doc/generic.texi
patching file gcc/doc/invoke.texi
patching file gcc/doc/sourcebuild.texi

There are still a lot of warnings in the .info build, but the overall gcc build completes. I have not retested tar -xf; patch; build.

I still am not in favor of putting this in LFS-7.3. It's so much easier to omit the .info build completely and, of course, there is no sense at all in building it in Chapter 5.

  -- Bruce

diff -Naur gcc-4.7.2/gcc/doc/cppopts.texi gcc-4.7.2-1/gcc/doc/cppopts.texi
--- gcc-4.7.2/gcc/doc/cppopts.texi      2011-12-20 20:44:13.000000000 +0000
+++ gcc-4.7.2-1/gcc/doc/cppopts.texi    2013-02-23 17:09:08.000000000 +0000
@@ -803,7 +803,7 @@
 Enable special code to work around file systems which only permit very
 short file names, such as MS-DOS@.
 
-@itemx --help
+@item --help
 @itemx --target-help
 @opindex help
 @opindex target-help
diff -Naur gcc-4.7.2/gcc/doc/gcc.texi gcc-4.7.2-1/gcc/doc/gcc.texi
--- gcc-4.7.2/gcc/doc/gcc.texi  2010-06-09 23:46:33.000000000 +0000
+++ gcc-4.7.2-1/gcc/doc/gcc.texi        2013-02-23 17:15:50.000000000 +0000
@@ -86,9 +86,13 @@
 @item GNU Press
 @tab Website: www.gnupress.org
 @item a division of the
-@tab General: @tex press@@gnu.org @end tex
+@tab General: 
+@tex press@@gnu.org 
+@end tex
 @item Free Software Foundation
-@tab Orders:  @tex sales@@gnu.org @end tex
+@tab Orders:  
+@tex sales@@gnu.org 
+@end tex
 @item 51 Franklin Street, Fifth Floor
 @tab Tel 617-542-5942
 @item Boston, MA 02110-1301 USA
diff -Naur gcc-4.7.2/gcc/doc/generic.texi gcc-4.7.2-1/gcc/doc/generic.texi
--- gcc-4.7.2/gcc/doc/generic.texi      2011-12-23 22:07:16.000000000 +0000
+++ gcc-4.7.2-1/gcc/doc/generic.texi    2013-02-24 00:27:55.000000000 +0000
@@ -1415,13 +1415,13 @@
 not matter.  The type of the operands and that of the result are
 always of @code{BOOLEAN_TYPE} or @code{INTEGER_TYPE}.
 
-@itemx POINTER_PLUS_EXPR
+@item POINTER_PLUS_EXPR
 This node represents pointer arithmetic.  The first operand is always
 a pointer/reference type.  The second operand is always an unsigned
 integer type compatible with sizetype.  This is the only binary
 arithmetic operand that can operate on pointer types.
 
-@itemx PLUS_EXPR
+@item PLUS_EXPR
 @itemx MINUS_EXPR
 @itemx MULT_EXPR
 These nodes represent various binary arithmetic operations.
diff -Naur gcc-4.7.2/gcc/doc/invoke.texi gcc-4.7.2-1/gcc/doc/invoke.texi
--- gcc-4.7.2/gcc/doc/invoke.texi       2012-09-14 20:45:27.000000000 +0000
+++ gcc-4.7.2-1/gcc/doc/invoke.texi     2013-02-24 00:30:24.000000000 +0000
@@ -5179,7 +5179,7 @@
 e.g. With -fdbg-cnt=dce:10,tail_call:0
 dbg_cnt(dce) will return true only for first 10 invocations
 
-@itemx -fenable-@var{kind}-@var{pass}
+@item -fenable-@var{kind}-@var{pass}
 @itemx -fdisable-@var{kind}-@var{pass}=@var{range-list}
 @opindex fdisable-
 @opindex fenable-
@@ -5327,11 +5327,11 @@
 @option{-fdump-rtl-ce3} enable dumping after the three
 if conversion passes.
 
-@itemx -fdump-rtl-cprop_hardreg
+@item -fdump-rtl-cprop_hardreg
 @opindex fdump-rtl-cprop_hardreg
 Dump after hard register copy propagation.
 
-@itemx -fdump-rtl-csa
+@item -fdump-rtl-csa
 @opindex fdump-rtl-csa
 Dump after combining stack adjustments.
 
@@ -5342,11 +5342,11 @@
 @option{-fdump-rtl-cse1} and @option{-fdump-rtl-cse2} enable dumping after
 the two common sub-expression elimination passes.
 
-@itemx -fdump-rtl-dce
+@item -fdump-rtl-dce
 @opindex fdump-rtl-dce
 Dump after the standalone dead code elimination passes.
 
-@itemx -fdump-rtl-dbr
+@item -fdump-rtl-dbr
 @opindex fdump-rtl-dbr
 Dump after delayed branch scheduling.
 
@@ -5391,7 +5391,7 @@
 @opindex fdump-rtl-initvals
 Dump after the computation of the initial value sets.
 
-@itemx -fdump-rtl-into_cfglayout
+@item -fdump-rtl-into_cfglayout
 @opindex fdump-rtl-into_cfglayout
 Dump after converting to cfglayout mode.
 
@@ -5421,7 +5421,7 @@
 @opindex fdump-rtl-rnreg
 Dump after register renumbering.
 
-@itemx -fdump-rtl-outof_cfglayout
+@item -fdump-rtl-outof_cfglayout
 @opindex fdump-rtl-outof_cfglayout
 Dump after converting from cfglayout mode.
 
@@ -5433,7 +5433,7 @@
 @opindex fdump-rtl-postreload
 Dump after post-reload optimizations.
 
-@itemx -fdump-rtl-pro_and_epilogue
+@item -fdump-rtl-pro_and_epilogue
 @opindex fdump-rtl-pro_and_epilogue
 Dump after generating the function prologues and epilogues.
 
diff -Naur gcc-4.7.2/gcc/doc/sourcebuild.texi 
gcc-4.7.2-1/gcc/doc/sourcebuild.texi
--- gcc-4.7.2/gcc/doc/sourcebuild.texi  2011-07-25 16:44:22.000000000 +0000
+++ gcc-4.7.2-1/gcc/doc/sourcebuild.texi        2013-02-24 00:28:36.000000000 
+0000
@@ -676,7 +676,7 @@
 @code{lang_checks}.
 
 @table @code
-@itemx all.cross
+@item all.cross
 @itemx start.encap
 @itemx rest.encap
 FIXME: exactly what goes in each of these targets?
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to