From: christophe.jarry@ouvaton.org
To: gcc-help@gcc.gnu.org
Subject: gcc.texi: problem generating documentation
Date: Wed, 03 Mar 2010 11:41:00 -0000 [thread overview]
Message-ID: <20100303124143.slx1yy4z6sk48c08@horde.ocsa-data.net> (raw)
Hello,
I am contributing to the gNewSense project and I am currently looking
for a way to create GCC documentation in info format for metad version
of gNewSense.
I found GCC documentation source at
http://gcc.gnu.org/onlinedocs/docs-sources.tar.gz, then extracted it
under /tmp.
But I have a problem when I want to makeinfo 'gcc.texi' file:
user@machine /tmp/gcc/gcc/doc
$ makeinfo gcc.texi
gcc.texi:25: @include 'gcc-common.texi': No such file or directory
[...]
'gcc-common.texi' is in fact in the ./include
(/tmp/gcc/gcc/doc/include in this case) directory, while gcc.texi
calls it with a '@include gcc-common.texi'.
I browsed gcc and gcc-help mailing-lists archives but didn't find a
way to figure this out. A web search with 'gcc-common.texi' and
'makeinfo' keywords wasn't more successful.
Is that a bug?
Other files call 'gcc-common.texi':
cpp.texi
cppinternals.texi
gccint.texi
install.texi
sourcebuild.texi
Thanks in advance for your help,
Christophe
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
next reply other threads:[~2010-03-03 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 11:41 christophe.jarry [this message]
2010-03-03 15:44 ` Ian Lance Taylor
2010-03-03 23:07 ` Christophe Jarry
2010-03-04 0:39 ` Ian Lance Taylor
2010-03-04 12:55 ` christophe.jarry
2010-03-05 15:46 ` Ian Lance Taylor
[not found] ` <4B7A6CC9992C4E4FB188D02872C90A6B134EFC@nambxv01a.corp.adobe.com>
2010-03-09 22:29 ` Christophe Jarry
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=20100303124143.slx1yy4z6sk48c08@horde.ocsa-data.net \
--to=christophe.jarry@ouvaton.org \
--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).