From: "Kelley Cook" <kelleycook@wideopenwest.com>
To: "Gerald Pfeifer" <gp@suse.de>, "Gunther Nikl" <gni@gecko.de>
Cc: "GCC Mailing List" <gcc@gcc.gnu.org>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Kelley Cook" <kcook@gcc.gnu.org>
Subject: [Committed] Install gccinstall.info (was fastjar.info not installed any longer?)
Date: Sun, 30 Nov 2003 02:47:00 -0000 [thread overview]
Message-ID: <200311300107.hAU177F28004@pop-6.dnv.wideopenwest.com> (raw)
In-Reply-To: <20031127103510.GA62621@lorien.int.gecko.de>
On Thu, 27 Nov 2003 11:35:10 +0100, Gunther Nikl wrote:
>On Thu, Nov 27, 2003 at 10:45:48AM +0100, Gerald Pfeifer wrote:
>> On current mainline (with --enable-languages=c,c++,objc,java) fastjar.info
>> is not installed any longer, even though it is created in the object tree.
> The same is true for gccinstall.info.
The gccinstall.info portion is fixed with a one-liner.
i686-pc-cygwin:
make bootstrap
make install
Committed under the obvious rule.
Kelley Cook
2003-11-29 Kelley Cook <kcook@gcc.gnu.org>
* Makefile.in (install-info): Install gccinstall.info too.
Index: Makefile.in
===================================================================
RCS file: /cvs/gcc/gcc/gcc/Makefile.in,v
retrieving revision 1.1201
diff -u -p -r1.1201 Makefile.in
--- Makefile.in 26 Nov 2003 19:04:18 -0000 1.1201
+++ Makefile.in 30 Nov 2003 01:01:56 -0000
@@ -2980,6 +2980,7 @@ install-info:: doc installdirs \
$(DESTDIR)$(infodir)/cpp.info \
$(DESTDIR)$(infodir)/gcc.info \
$(DESTDIR)$(infodir)/cppinternals.info \
+ $(DESTDIR)$(infodir)/gccinstall.info \
$(DESTDIR)$(infodir)/gccint.info
$(DESTDIR)$(infodir)/%.info: $(docobjdir)/%.info installdirs
parent reply other threads:[~2003-11-30 1:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20031127103510.GA62621@lorien.int.gecko.de>]
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=200311300107.hAU177F28004@pop-6.dnv.wideopenwest.com \
--to=kelleycook@wideopenwest.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gni@gecko.de \
--cc=gp@suse.de \
--cc=kcook@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).