From: James Clark <james.clark@arm.com>
To: arnaldo.melo@gmail.com, shikemeng@huawei.com
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
James Clark <james.clark@arm.com>
Subject: [PATCH 1/1] perf tools: fix compilation on Arm
Date: Thu, 2 Apr 2020 14:41:28 +0100 [thread overview]
Message-ID: <20200402134128.14493-2-james.clark@arm.com> (raw)
In-Reply-To: <20200402134128.14493-1-james.clark@arm.com>
The commit "perf report: Fix arm64 gap between kernel
start and module end" introduces the following build
error with GCC 7.3.0 on Arm:
"error: implicit declaration of function ‘strchr’"
Adding the required header fixes the issue.
Signed-off-by: James Clark <james.clark@arm.com>
---
tools/perf/arch/arm64/util/machine.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/arch/arm64/util/machine.c b/tools/perf/arch/arm64/util/machine.c
index 94745131e89a..d41b27e781d3 100644
--- a/tools/perf/arch/arm64/util/machine.c
+++ b/tools/perf/arch/arm64/util/machine.c
@@ -1,6 +1,7 @@
// SPDX-License-Identifier: GPL-2.0
#include <stdio.h>
+#include <string.h>
#include "debug.h"
#include "symbol.h"
--
2.17.1
next prev parent reply other threads:[~2020-04-02 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 7:41 [PATCH] perf report: Fix arm64 gap between kernel start and module end Kemeng Shi
2020-03-30 13:11 ` Arnaldo Carvalho de Melo
2020-03-30 13:18 ` Arnaldo Carvalho de Melo
2020-04-02 13:41 ` [PATCH 0/1] perf tools: fix compilation on Arm James Clark
2020-04-02 13:41 ` James Clark [this message]
2021-02-09 12:40 ` [PATCH] perf report: Fix arm64 gap between kernel start and module end Arnaldo Carvalho de Melo
2021-02-09 12:46 ` Arnaldo Carvalho de Melo
2020-03-31 4:13 ` Kemeng Shi
2020-04-04 8:41 ` [tip: perf/urgent] perf symbols: " tip-bot2 for Kemeng Shi
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=20200402134128.14493-2-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=shikemeng@huawei.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;
as well as URLs for NNTP newsgroup(s).