From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail•com>
To: Naresh Kamboju <naresh.kamboju@linaro•org>
Cc: Peter Zijlstra <peterz@infradead•org>,
mingo@redhat•com, alexander.shishkin@linux•intel.com,
jolsa@redhat•com, namhyung@kernel•org,
open list <linux-kernel@vger•kernel.org>,
lkft-triage@lists•linaro.org,
Linux-Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: perf build failed on linux -next on i386 build
Date: Thu, 26 Sep 2019 14:36:48 -0300 [thread overview]
Message-ID: <20190926173648.GA31477@kernel.org> (raw)
In-Reply-To: <CA+G9fYu0hkS+NdwX38DNTygV1A7eebvjZvWvFUTfL=f3_4m=Dw@mail.gmail.com>
Em Thu, Sep 26, 2019 at 10:59:41PM +0530, Naresh Kamboju escreveu:
> perf build failed on linux -next on i386 build
>
> build error:
> perf-in.o: In function `libunwind__x86_reg_id':
> tools/perf/util/libunwind/../../arch/x86/util/unwind-libunwind.c:109:
> undefined reference to `pr_err'
> tools/perf/util/libunwind/../../arch/x86/util/unwind-libunwind.c:109:
> undefined reference to `pr_err'
Can you try with the following patch?
diff --git a/tools/perf/arch/x86/util/unwind-libunwind.c b/tools/perf/arch/x86/util/unwind-libunwind.c
index 05920e3edf7a..47357973b55b 100644
--- a/tools/perf/arch/x86/util/unwind-libunwind.c
+++ b/tools/perf/arch/x86/util/unwind-libunwind.c
@@ -1,11 +1,11 @@
// SPDX-License-Identifier: GPL-2.0
#include <errno.h>
+#include "../../util/debug.h"
#ifndef REMOTE_UNWIND_LIBUNWIND
#include <libunwind.h>
#include "perf_regs.h"
#include "../../util/unwind.h"
-#include "../../util/debug.h"
#endif
#ifdef HAVE_ARCH_X86_64_SUPPORT
next prev parent reply other threads:[~2019-09-26 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 17:29 perf build failed on linux -next on i386 build Naresh Kamboju
2019-09-26 17:36 ` Arnaldo Carvalho de Melo [this message]
2019-09-26 20:35 ` Naresh Kamboju
2019-09-27 15:42 ` Arnaldo Carvalho de Melo
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=20190926173648.GA31477@kernel.org \
--to=arnaldo.melo@gmail$(echo .)com \
--cc=alexander.shishkin@linux$(echo .)intel.com \
--cc=jolsa@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=mingo@redhat$(echo .)com \
--cc=namhyung@kernel$(echo .)org \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=peterz@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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