From: christophe.jarry@ouvaton.org
To: gcc-help@gcc.gnu.org
Subject: Re: gcc.texi: problem generating documentation
Date: Thu, 04 Mar 2010 12:55:00 -0000 [thread overview]
Message-ID: <20100304135513.nouxbixggk0sg04o@horde.ocsa-data.net> (raw)
In-Reply-To: <mcrlje8j4ya.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
Quoting Ian Lance Taylor <iant@google.com>:
> Christophe Jarry <christophe.jarry@ouvaton.org> writes:
>
>> I did this in 'gcc-4.4.3/gcc/doc' folder extracted from gcc source, as
>> well as in 'gcc/gcc/doc' folder extracted from gcc _doc_ source:
>
> You need to first run configure in a new empty directory as described
> in the gcc installation instructions. Then you can run "make info" in
> the gcc subdirectory.
>
> Ian
>
Thanks Ian, it seems to work when compiling from source code, in
gcc-4.4.3/ directory:
./configure
make info
Then, I have a gcc-4.4.3/gcc/doc/gcc.info file about 1.9M in size (ls
-s -h gcc.info).
Now, is it possible to build GCC documentation directly from
http://gcc.gnu.org/onlinedocs/docs-sources.tar.gz file, instead of
having to download GCC whole source code? From extracted
docs-sources.tar.gz file, I tried this:
cd gcc/gcc/doc
makeinfo -I include/ gcc.texi
But then, I have the following error message:
include//gcc-common.texi:12: @include `gcc-vers.texi': No such file
or directory.
gcc.texi:125: warning: undefined flag: version-GCC.
/cygdrive/d/cj/gnu-linux/gcc/gcc/doc//invoke.texi:1301: warning:
undefined flag: srcdir.
/cygdrive/d/cj/gnu-linux/gcc/gcc/doc//invoke.texi:1300: @include
`{No value for `srcdir'}/../libiberty/at-file.texi': No such file or
directory.
/cygdrive/d/cj/gnu-linux/gcc/gcc/doc//bugreport.texi:91: warning:
undefined flag: BUGURL.
makeinfo: Removing output file
`/cygdrive/d/cj/gnu-linux/gcc/gcc/doc/gcc.info' due to errors; use
--force to preserve.
Notes:
- there is no 'gcc-vers.texi' file in the entire gcc/ directory,
- there is an 'at-file.texi' in gcc/libiberty/, but I don't know how
to define 'srcdir' flag?
Thanks for your help,
Christophe
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
next prev parent reply other threads:[~2010-03-04 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 11:41 christophe.jarry
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 [this message]
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=20100304135513.nouxbixggk0sg04o@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).