diff mbox

[doc,committed] clean up redundant cpp option documentation

Message ID 6898274.a7gBuGsFPU@arcturus.home
State New
Headers show

Commit Message

Eric Botcazou Dec. 26, 2016, 9:38 a.m. UTC
> eric@arcturus:~/build/gcc/native/gcc> make doc
> if [ xinfo = xinfo ]; then \
>         makeinfo --split-size=5000000 --split-size=5000000 --no-split -I .
> -I /home/eric/svn/gcc/gcc/doc \
>                 -I /home/eric/svn/gcc/gcc/doc/include -o doc/cpp.info
> /home/eric/svn/gcc/gcc/doc/cpp.texi; \
> fi
> /home/eric/svn/gcc/gcc/doc/cpp.texi:4296: @command expected braces.
> /home/eric/svn/gcc/gcc/doc/cpp.texi:4296: Misplaced {.
> /home/eric/svn/gcc/gcc/doc/cpp.texi:4296: Misplaced }.
> /home/eric/svn/gcc/gcc/doc//cppopts.texi:4296: @code missing close brace.
> makeinfo: Removing output file `doc/cpp.info' due to errors; use --force to
> preserve.
> Makefile:3145: recipe for target 'doc/cpp.info' failed
> make: *** [doc/cpp.info] Error 1

Fixed thusly, applied on the mainline.


	* doc/cpp.texi (Invocation): Remove space in command.

Comments

Sandra Loosemore Dec. 26, 2016, 6:13 p.m. UTC | #1
On 12/26/2016 02:38 AM, Eric Botcazou wrote:
>> eric@arcturus:~/build/gcc/native/gcc> make doc
>> if [ xinfo = xinfo ]; then \
>>          makeinfo --split-size=5000000 --split-size=5000000 --no-split -I .
>> -I /home/eric/svn/gcc/gcc/doc \
>>                  -I /home/eric/svn/gcc/gcc/doc/include -o doc/cpp.info
>> /home/eric/svn/gcc/gcc/doc/cpp.texi; \
>> fi
>> /home/eric/svn/gcc/gcc/doc/cpp.texi:4296: @command expected braces.
>> /home/eric/svn/gcc/gcc/doc/cpp.texi:4296: Misplaced {.
>> /home/eric/svn/gcc/gcc/doc/cpp.texi:4296: Misplaced }.
>> /home/eric/svn/gcc/gcc/doc//cppopts.texi:4296: @code missing close brace.
>> makeinfo: Removing output file `doc/cpp.info' due to errors; use --force to
>> preserve.
>> Makefile:3145: recipe for target 'doc/cpp.info' failed
>> make: *** [doc/cpp.info] Error 1
>
> Fixed thusly, applied on the mainline.
>
>
> 	* doc/cpp.texi (Invocation): Remove space in command.

This is very strange; I didn't get that error.  We've got makeinfo 6.1 
(Feb 2016) installed here.  Are you using a newer or older version?

-Sandra
Eric Botcazou Dec. 26, 2016, 6:19 p.m. UTC | #2
> This is very strange; I didn't get that error.  We've got makeinfo 6.1
> (Feb 2016) installed here.  Are you using a newer or older version?

It's makeinfo 4.13 (from the vendor).
Sandra Loosemore Dec. 26, 2016, 8:29 p.m. UTC | #3
On 12/26/2016 11:19 AM, Eric Botcazou wrote:
>> This is very strange; I didn't get that error.  We've got makeinfo 6.1
>> (Feb 2016) installed here.  Are you using a newer or older version?
>
> It's makeinfo 4.13 (from the vendor).

Hmmm, that's 8 years old, the last release from before the 
reimplementation into Perl (starting with version 5).

Meanwhile install.texi documents (and configure.ac checks for) version 
4.7 as the earliest supported version.  That's a release from 2004, and 
the GCC requirement has been in place since 2008.  I guess it is OK to 
leave it like that unless/until we make an explicit decision to use some 
features only supported in newer versions, but I do worry that we won't 
be testing compatibility with such old Texinfo versions as developers 
shift to newer versions in their own environments.

-Sandra
Eric Botcazou Dec. 26, 2016, 9:21 p.m. UTC | #4
> Hmmm, that's 8 years old, the last release from before the
> reimplementation into Perl (starting with version 5).

I see, this may explain why the vendor still ship it then.
diff mbox

Patch

Index: doc/cpp.texi
===================================================================
--- doc/cpp.texi	(revision 243924)
+++ doc/cpp.texi	(working copy)
@@ -4293,7 +4293,7 @@  In GCC, the preprocessor is actually integrated wi
 rather than a separate program, and both of these commands invoke
 GCC and tell it to stop after the preprocessing phase.
 
-The @command {cpp} options listed here are also accepted by
+The @command{cpp} options listed here are also accepted by
 @command{gcc} and have the same meaning.  Likewise the @command{cpp}
 command accepts all the usual @command{gcc} driver options, although those
 pertaining to compilation phases after preprocessing are ignored.