From: Jack Mitchell <ml@communistcode.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
Subject: [PATCH] libtraceevent: remove hard coded include to /usr/local/include in Makefile
Date: Fri, 8 Mar 2013 11:21:52 +0000 [thread overview]
Message-ID: <1362741712-21308-1-git-send-email-ml@communistcode.co.uk> (raw)
From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
having /usr/local/include hardcoded into the makefile is not necessary as this
is automatically included by GCC. It also infects cross-compile builds with the
host systems includes.
Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
---
tools/lib/traceevent/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/lib/traceevent/Makefile b/tools/lib/traceevent/Makefile
index a20e320..0b0a907 100644
--- a/tools/lib/traceevent/Makefile
+++ b/tools/lib/traceevent/Makefile
@@ -122,7 +122,7 @@ export Q VERBOSE
EVENT_PARSE_VERSION = $(EP_VERSION).$(EP_PATCHLEVEL).$(EP_EXTRAVERSION)
-INCLUDES = -I. -I/usr/local/include $(CONFIG_INCLUDES)
+INCLUDES = -I. $(CONFIG_INCLUDES)
# Set compile option CFLAGS if not set elsewhere
CFLAGS ?= -g -Wall
--
1.8.1.5
next reply other threads:[~2013-03-08 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 11:21 Jack Mitchell [this message]
2013-03-11 8:08 ` [PATCH] libtraceevent: remove hard coded include to /usr/local/include in Makefile Namhyung Kim
2013-03-18 10:54 ` [tip:perf/urgent] libtraceevent: Remove hard coded include to / usr/local/include " tip-bot for Jack Mitchell
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=1362741712-21308-1-git-send-email-ml@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jack.mitchell@dbbroadcast.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.