From: tip-bot for Liming Wang <liming.wang@windriver.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
fweisbec@gmail.com, xiaoguangrong@cn.fujitsu.com,
tglx@linutronix.de, liming.wang@windriver.com, mingo@elte.hu
Subject: [tip:perf/core] perf tools: Fix _GNU_SOURCE macro related strndup() build error
Date: Wed, 2 Dec 2009 08:30:53 GMT [thread overview]
Message-ID: <tip-c19e33aa840e9202ef8d4c93056b59f3edc2208d@git.kernel.org> (raw)
In-Reply-To: <1259734306-26323-1-git-send-email-liming.wang@windriver.com>
Commit-ID: c19e33aa840e9202ef8d4c93056b59f3edc2208d
Gitweb: http://git.kernel.org/tip/c19e33aa840e9202ef8d4c93056b59f3edc2208d
Author: Liming Wang <liming.wang@windriver.com>
AuthorDate: Wed, 2 Dec 2009 14:11:46 +0800
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Wed, 2 Dec 2009 09:24:56 +0100
perf tools: Fix _GNU_SOURCE macro related strndup() build error
strndup is a GNU extension. So dont include string.h without
defining _GNU_SOURCE (it results in a compile error otherwise).
Remove these includes as util.h does it already.
Signed-off-by: Liming Wang <liming.wang@windriver.com>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
Acked-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: peterz@infradead.org
Cc: mhiramat@redhat.com
LKML-Reference: <1259734306-26323-1-git-send-email-liming.wang@windriver.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
tools/perf/util/string.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/string.c b/tools/perf/util/string.c
index 0977cf4..f24a8cc 100644
--- a/tools/perf/util/string.c
+++ b/tools/perf/util/string.c
@@ -1,5 +1,3 @@
-#include <string.h>
-#include <stdlib.h>
#include "string.h"
#include "util.h"
prev parent reply other threads:[~2009-12-02 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 6:11 [PATCH] perf tools: Add _GNU_SOURCE macro for strndup() Liming Wang
2009-12-02 8:04 ` Xiao Guangrong
2009-12-02 8:03 ` Wang Liming
2009-12-02 8:30 ` tip-bot for Liming Wang [this message]
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=tip-c19e33aa840e9202ef8d4c93056b59f3edc2208d@git.kernel.org \
--to=liming.wang@windriver.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=xiaoguangrong@cn.fujitsu.com \
/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