From: serge fukanchik <fuxx@mail.ru>
To: gcc-help@gcc.gnu.org
Subject: Documentation compiling errors
Date: Wed, 17 Nov 2004 13:55:00 -0000 [thread overview]
Message-ID: <E1CUQHi-0006Ts-00.fuxx-mail-ru@f29.mail.ru> (raw)
When compiling gcc on windows using mingw i got several
erorrs concerning 'Cross reference to nonexistent node'
in cpp.texi:
in @synindex.oc/cpp.texi:50: Unknown index `vr' and/or `op
Predefined Macros'.p.texi:3211: Cross reference to nonexistent node `Standard
Prescan'.gcc/doc/cpp.texi:1410: Cross reference to nonexistent node `Argument
Headers'.gcc/doc/cpp.texi:1068: Cross reference to nonexistent node `Once-Only
from previous versions'.i:578: Cross reference to nonexistent node `Differences
Operation'.c/doc/cpp.texi:573: Cross reference to nonexistent node `Include
Mode'.cc/gcc/doc/cpp.texi:231: Cross reference to nonexistent node `Traditional
makeinfo: Removing output file `doc/cpp.info' due to errors; use --force to preserve.
little investigation gives reason: `@ref{' can not be span across several lines.
I have makeinfo version 4.3
Is this error, or shall i upgrade my texinfo?
---
Serge
reply other threads:[~2004-11-17 13:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1CUQHi-0006Ts-00.fuxx-mail-ru@f29.mail.ru \
--to=fuxx@mail.ru \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).