From: Daniel Egger <degger@fhm.edu>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: GCC Mailinglist <gcc@gcc.gnu.org>
Subject: Re: Building with --enable-languages problematic
Date: Thu, 11 Oct 2001 07:38:00 -0000 [thread overview]
Message-ID: <1002803923.1374.3.camel@sonja> (raw)
In-Reply-To: <Pine.BSF.4.33.0110092222370.94202-100000@deneb.dbai.tuwien.ac.at>
Am Die, 2001-10-09 um 22.23 schrieb 1002659025:
> I don't understand. Our web page documentation and the HTML and
> ASCII docs shipped with releases all are generated from install.texi,
> so you can easily access the install docs immediately.
FWIW I prefer offline documentation over online documentation because
I have to pay access to the WWW per minute.
> Or did I misunderstand your problem?
IMHO important information to compile a software should always be
put into some sort of a textfile in the toplevel directory to guide
the user through the building process. Having the information in the
compiled docs is nice though it won't help if you fail to build at
all.
--
Servus,
Daniel
next prev parent reply other threads:[~2001-10-11 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 12:24 Daniel Egger
2001-10-09 12:29 ` guerby
2001-10-09 12:30 ` Daniel Jacobowitz
2001-10-09 13:06 ` Daniel Egger
2001-10-09 13:25 ` Gerald Pfeifer
2001-10-11 7:38 ` Daniel Egger [this message]
2001-10-12 13:56 ` Gerald Pfeifer
2001-10-09 13:27 ` Phil Edwards
2001-10-13 10:36 ` Daniel Egger
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=1002803923.1374.3.camel@sonja \
--to=degger@fhm.edu \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).