From: Jim Wilson <wilson@codesourcery.com>
To: christophe.jarry@ouvaton.org
Cc: gcc@gnu.org
Subject: Re: GCC documentation: info format
Date: Fri, 09 Apr 2010 18:18:00 -0000 [thread overview]
Message-ID: <4BBF6EDB.9020603@codesourcery.com> (raw)
In-Reply-To: <20100409140846.60xsm71qo8s4cc80@horde.ocsa-data.net>
On 04/09/2010 05:08 AM, christophe.jarry@ouvaton.org wrote:
> Where may I find gcc-vers.texi?
It is created by the install.texi2html shell script, which also creates
the HTML output files that go on the web site. You can probably modify
this script to generate info files instead, but as Diego mentioned, the
recommended way to produce info files is to configure and build a full
source tree.
Don't forget about the libstdc++-v3 docs which are not in the
docs-sources.tar.gz file. Also, don't forget about the other docs which
are not in the gcc/doc directory. "make info" in a build tree takes
care of this stuff for you.
Jim
next prev parent reply other threads:[~2010-04-09 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 12:59 christophe.jarry
2010-04-09 16:00 ` Diego Novillo
2010-04-09 18:18 ` Jim Wilson [this message]
2010-04-09 22:16 ` Jim Wilson
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=4BBF6EDB.9020603@codesourcery.com \
--to=wilson@codesourcery.com \
--cc=christophe.jarry@ouvaton.org \
--cc=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).