From: Phil Edwards <pedwards@disaster.jaj.com>
To: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [RFA] Patch for: Re: Why don't we provide a default INSTALL_SCRIPT in gcc/Makefile.in?
Date: Mon, 03 Dec 2001 06:39:00 -0000 [thread overview]
Message-ID: <20011203094324.A16339@disaster.jaj.com> (raw)
Alexandre Oliva wrote:
> On Nov 27, 2001, "H . J . Lu" <hjl@lucon.org> wrote:
> > This patch
> > http://gcc.gnu.org/ml/gcc-bugs/2001-11/msg00221.html
>
> > uses INSTALL_SCRIPT without providing a default. As the result, I
> > can no longer do
>
> > # cd gcc
> > # make install
>
> Hmm, indeed.
>
> Would one of you please post a patch that copies the definition of:
>
> INSTALL_SCRIPT = @INSTALL@
>
> from the top-level Makefile.in into gcc/Makefile.in?
I just got bit by this same bug. So, scratching this itch:
"cd gcc; make install" works now. Previously it would break on gccbug.
Index: Makefile.in
===================================================================
RCS file: /home/pme/Repositories/GCC/gcc/gcc/Makefile.in,v
retrieving revision 1.796
diff -u -3 -r1.796 Makefile.in
--- Makefile.in 30 Nov 2001 04:38:41 -0000 1.796
+++ Makefile.in 3 Dec 2001 14:35:27 -0000
@@ -121,6 +121,7 @@
# These permit overriding just for certain files.
INSTALL_PROGRAM = @INSTALL_PROGRAM@
INSTALL_DATA = @INSTALL_DATA@
+INSTALL_SCRIPT = @INSTALL@
MAKEINFO = @MAKEINFO@
MAKEINFOFLAGS =
TEXI2DVI = texi2dvi
next reply other threads:[~2001-12-03 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 6:39 Phil Edwards [this message]
2001-12-04 0:54 ` Alexandre Oliva
2001-12-04 15:44 ` Phil Edwards
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=20011203094324.A16339@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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).