From: hjl@lucon.org (H.J. Lu)
To: pfeifer@dbai.tuwien.ac dot@(Gerald Pfeifer)
Cc: law@cygnus.com, egcs@cygnus.com
Subject: Re: egrep -i haifa INSTALL install.texi
Date: Tue, 02 Dec 1997 23:24:00 -0000 [thread overview]
Message-ID: <m0xd4qP-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <Pine.GSO.3.96.971202223251.14537A-100000@alcyone.dbai.tuwien.ac.at>
>
> On Sun, 30 Nov 1997, Jeffrey A Law wrote:
> >> ...in egcs-971127/gcc only produces matches in install.texi, not a single
> >> one in INSTALL.
> > gcc/INSTALL is basically out of date and depreciated for egcs.
>
> Well, but in that case it should be either completely removed or --
> probably better -- contain a pointer to install.texi:
>
> "This file, which used to contain installation instructions for
> gcc/egcs, has been superseded by install.texi. Please check the
> information there."
>
>
> IMHO, out of all possible scenarios, an out-of-date gcc/INSTALL is surely
> the worst: Once having found INSTALL, most people won't look any further,
> thus using obsolete resp. incomplete information.
>
Here is the patch in gcc2. It is very straight forward to rebuild
INSTALL from install.texi. Why not do it?
H.J.
---
Sun Aug 3 17:27:44 1997 H.J. Lu (hjl@gnu.ai.mit.edu)
* Makefile.in (INSTALL): Build in $(srcdir).
--- Makefile.in.orig Tue Dec 2 18:43:46 1997
+++ Makefile.in Tue Dec 2 18:44:17 1997
@@ -2011,8 +2011,8 @@
INSTALL: $(srcdir)/install1.texi $(srcdir)/install.texi
- $(MAKEINFO) -D INSTALLONLY --no-header --no-split \
- $(srcdir)/install1.texi -o INSTALL
+ cd $(srcdir); $(MAKEINFO) -D INSTALLONLY --no-header \
+ --no-split install1.texi -o INSTALL
#\f
# Deletion of files made during compilation.
# There are four levels of this:
prev parent reply other threads:[~1997-12-02 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-29 13:40 Gerald Pfeifer
1997-11-30 18:55 ` Jeffrey A Law
1997-12-01 11:32 ` Joe Buck
1997-12-01 11:33 ` Jeffrey A Law
1997-12-02 16:29 ` Gerald Pfeifer
1997-12-02 18:18 ` Jeffrey A Law
1997-12-02 23:24 ` H.J. Lu [this message]
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=m0xd4qP-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=pfeifer@dbai.tuwien.ac \
/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).