From: Ian Lance Taylor <iant@google.com>
To: christophe.jarry@ouvaton.org
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc.texi: problem generating documentation
Date: Fri, 05 Mar 2010 15:46:00 -0000 [thread overview]
Message-ID: <mcrtysug4aa.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <20100304135513.nouxbixggk0sg04o@horde.ocsa-data.net> (christophe jarry's message of "Thu\, 04 Mar 2010 13\:55\:13 +0100")
christophe.jarry@ouvaton.org writes:
> 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?
I have no idea. I don't know what creates that tar file. If you want
to find out what creates that file and fix it up so that "make info"
works, I'm sure that help somebody in the future. Note that simply
running "makeinfo" is not likely to be a useful goal; the useful goal
is "make info".
> - there is no 'gcc-vers.texi' file in the entire gcc/ directory,
gcc-vers.texi is created at "make" time. There is a rule in
gcc/Makefile.
> - there is an 'at-file.texi' in gcc/libiberty/, but I don't know how
> to define 'srcdir' flag?
srcdir is normally set by gcc-vers.texi.
Ian
next prev parent reply other threads:[~2010-03-05 15:46 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
2010-03-05 15:46 ` Ian Lance Taylor [this message]
[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=mcrtysug4aa.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=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).