Hmm okay. Doesn't seem to work for me on latest master at least.

Here's the error i'm getting with makeinfo 4.13:
../../gcc/doc//invoke.texi:249: warning: unlikely character , in @var.
../../gcc/doc//invoke.texi:3801: warning: unlikely character , in @var.
../../gcc/doc//invoke.texi:5247: warning: `.' or `,' must follow @xref, not `a'. ../../gcc/doc//invoke.texi:20947: warning: `.' or `,' must follow @xref, not `f'. ../../gcc/doc//extend.texi:9990: warning: `.' or `,' must follow @xref, not `)'. ../../gcc/doc//extend.texi:9990: warning: for cross-references in parentheses, use @pxref. ../../gcc/doc//extend.texi:10670: First argument to cross-reference may not be empty. ../../gcc/doc//extend.texi:10692: First argument to cross-reference may not be empty. ../../gcc/doc//extend.texi:12590: warning: `.' or `,' must follow @xref, not `)'. ../../gcc/doc//extend.texi:12590: warning: for cross-references in parentheses, use @pxref. ../../gcc/doc//extend.texi:12594: warning: `.' or `,' must follow @xref, not `)'. ../../gcc/doc//extend.texi:12594: warning: for cross-references in parentheses, use @pxref.
../../gcc/doc//gcov.texi:1080: @anchor expected braces.
../../gcc/doc//gcov.texi:1110: Unmatched `@end'.
../../gcc/doc//gcov.texi:1080: @anchor missing close brace.
../../gcc/doc//invoke.texi:17736: Cross reference to nonexistent node `gcov prime paths example' (perhaps incorrect sectioning?).
../../gcc/doc/gcc.texi:228: Misplaced {.
../../gcc/doc/gcc.texi:228: Misplaced }.
../../gcc/doc/gcc.texi:228: Multiline command @smallexample used improperly. makeinfo: Removing output file `doc/gcc.info' due to errors; use --force to preserve.

On 2025-06-08 17:07, Jeff Law wrote:
On 6/7/25 4:11 AM, Henrik Lindström wrote:
The build fails with older versions.

Signed-off-by: Henrik Lindström <hen...@lxm.se>
---
  gcc/configure    | 2 +-
  gcc/configure.ac | 2 +-
  2 files changed, 2 insertions(+), 2 deletions(-)
I think that was just a bug in our documentation that was subsequently fixed by Jan. AFAIK it's supposed to work with 4.13.

jeff

Reply via email to