From: Jie Zhang <jie@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Fix Makefile.in in data-directory
Date: Wed, 20 Oct 2010 12:09:00 -0000 [thread overview]
Message-ID: <4CBEDBF5.9060504@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
The current install rule in the Makefile.in of data-directory uses
recursive make but does not pass FLAGS_TO_PASS. This causes an issue
when people try to override prefix with command line option "make
install", i.e. data-directory will still be installed under the
configure time prefix. This patch fixes it. OK?
Regards,
--
Jie Zhang
CodeSourcery
[-- Attachment #2: gdb-fix-data-directory-Makefile.diff --]
[-- Type: text/x-patch, Size: 730 bytes --]
* data-directory/Makefile.in (install): Add dependency on
install-only. Delete code making it.
Index: data-directory/Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/data-directory/Makefile.in,v
retrieving revision 1.3
diff -u -p -r1.3 Makefile.in
--- data-directory/Makefile.in 13 Oct 2010 20:08:44 -0000 1.3
+++ data-directory/Makefile.in 20 Oct 2010 11:54:39 -0000
@@ -145,8 +145,7 @@ uninstall-python:
# time it takes for make to check that all is up to date.
# install-only is intended to address that need.
.PHONY: install
-install: all
- $(MAKE) install-only
+install: all install-only
.PHONY: install-only
install-only: install-syscalls install-python
next reply other threads:[~2010-10-20 12:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 12:09 Jie Zhang [this message]
2010-10-20 20:13 ` Doug Evans
2010-10-21 0:10 ` Jie Zhang
2010-10-21 0:14 ` Pedro Alves
2010-10-21 0:17 ` Jie Zhang
2010-10-21 0:29 ` Pedro Alves
2010-10-21 2:15 ` Jie Zhang
2010-10-21 2:30 ` Doug Evans
2010-10-21 5:11 ` Jie Zhang
2010-10-21 21:06 ` Doug Evans
2010-10-21 23:52 ` Jie Zhang
2010-10-21 10:07 ` Pedro Alves
2010-10-21 14:46 ` Joel Brobecker
2010-10-22 1:14 ` Tom Tromey
2010-10-21 21:08 ` Doug Evans
2010-10-22 1:11 ` Tom Tromey
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=4CBEDBF5.9060504@codesourcery.com \
--to=jie@codesourcery.com \
--cc=gdb-patches@sourceware.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