From: Jim Meyering <meyering@ascend.com>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com
Subject: Re: Does "make install" work?
Date: Fri, 26 Jun 1998 09:06:00 -0000 [thread overview]
Message-ID: <873ecsmj6d.fsf@eng.ascend.com> (raw)
In-Reply-To: <m0ypOJy-000265C@ocean.lucon.org>
hjl@lucon.org (H.J. Lu) writes:
| Hi,
|
| This is what I got with "make install". Any ideas?
...
| install-info: menu item `gcc' already exists, for file `gcc'
| install-info: menu item `gcc' already exists, for file `gcc'
| install-info: menu item `gcc' already exists, for file `gcc'
| make[1]: *** [install-info] Error 1
| make[1]: Leaving directory `/home/work/gnu/bin/egcs/gcc'
| make: *** [install-gcc] Error 2
Here's how I fixed it in my local copy:
Index: Makefile.in
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/Makefile.in,v
retrieving revision 1.138
diff -u -p -r1.138 Makefile.in
--- Makefile.in 1998/06/26 02:13:41 1.138
+++ Makefile.in 1998/06/26 12:37:34
@@ -2380,7 +2380,7 @@ install-info: doc installdirs lang.insta
realfile=`echo $$f | sed -e 's|.*/\([^/]*\)$$|\1|'`; \
$(INSTALL_DATA) $$f $(infodir)/$$realfile; \
if $(SHELL) -c 'install-info --version' >/dev/null 2>&1; then \
- install-info --dir-file=$(infodir)/dir $(infodir)/$$realfile; \
+ install-info --dir-file=$(infodir)/dir $(infodir)/$$realfile || true; \
else true; fi; \
done
-chmod a-x $(infodir)/cpp.info* $(infodir)/gcc.info*
next prev parent reply other threads:[~1998-06-26 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-25 23:46 H.J. Lu
1998-06-26 5:13 ` Andreas Schwab
1998-06-26 8:43 ` H.J. Lu
1998-06-26 9:23 ` Gerald Pfeifer
1998-06-26 18:46 ` Carlo Wood
1998-06-27 7:22 ` Gerald Pfeifer
1998-06-27 10:03 ` Jeffrey A Law
1998-06-26 18:46 ` Martin von Loewis
1998-06-26 9:06 ` Jim Meyering [this message]
1998-06-26 9:06 ` Manfred Hollstein
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=873ecsmj6d.fsf@eng.ascend.com \
--to=meyering@ascend.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.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).