From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@gmail.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH 9/9] perf tools: Fix compile error on x86_64 Ubuntu
Date: Sun, 8 Jan 2012 13:42:19 -0200 [thread overview]
Message-ID: <1326037339-31125-10-git-send-email-acme@infradead.org> (raw)
In-Reply-To: <1326037339-31125-1-git-send-email-acme@infradead.org>
From: Namhyung Kim <namhyung@gmail.com>
The ctype.h include is not needed here and it breaks build on some systems (at
least 64bit Ubuntu 10.04) like below. Just get rid of it.
CC util/trace-event-info.o
cc1: warnings being treated as errors
util/trace-event-info.c: In function ‘record_file’:
util/trace-event-info.c:192: error: implicit declaration of function ‘pwrite’
util/trace-event-info.c:192: error: nested extern declaration of ‘pwrite’
make: *** [util/trace-event-info.o] Error 1
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Joerg Roedel <joerg.roedel@amd.com>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/1326035430-7621-1-git-send-email-namhyung@gmail.com
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/util/trace-event-info.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/tools/perf/util/trace-event-info.c b/tools/perf/util/trace-event-info.c
index ac6830d..fc22cf5 100644
--- a/tools/perf/util/trace-event-info.c
+++ b/tools/perf/util/trace-event-info.c
@@ -18,7 +18,6 @@
*
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*/
-#include <ctype.h>
#include "util.h"
#include <dirent.h>
#include <mntent.h>
--
1.7.8.GIT
next prev parent reply other threads:[~2012-01-08 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 15:42 [GIT PULL 0/9] perf/core fixes and improvements Arnaldo Carvalho de Melo
2012-01-08 15:42 ` [PATCH 1/9] perf script: Add missing closedir() calls Arnaldo Carvalho de Melo
2012-01-08 15:42 ` [PATCH 2/9] perf test: Change type of '-v' option to INCR Arnaldo Carvalho de Melo
2012-01-08 15:42 ` [PATCH 3/9] perf top: Add error message for EMFILE Arnaldo Carvalho de Melo
2012-01-08 15:42 ` [PATCH 4/9] perf kmem: Add missing closedir() calls Arnaldo Carvalho de Melo
2012-01-08 15:42 ` [PATCH 5/9] perf kmem: Fix a memory leak Arnaldo Carvalho de Melo
2012-01-08 15:42 ` [PATCH 6/9] perf annotate: Fix usage string Arnaldo Carvalho de Melo
2012-01-08 15:42 ` [PATCH 7/9] perf annotate: Get rid of field_sep check Arnaldo Carvalho de Melo
2012-01-08 16:11 ` Namhyung Kim
2012-01-08 15:42 ` [PATCH 8/9] perf report: Fix --stdio output alignment when --showcpuutilization used Arnaldo Carvalho de Melo
2012-01-08 15:42 ` Arnaldo Carvalho de Melo [this message]
2012-01-08 16:02 ` [GIT PULL 0/9] perf/core fixes and improvements Ingo Molnar
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=1326037339-31125-10-git-send-email-acme@infradead.org \
--to=acme@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@gmail.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 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 NNTP newsgroup(s).