From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: perf tool failing to build for ARM
Date: Fri, 26 Sep 2014 17:25:31 +0100 [thread overview]
Message-ID: <20140926162530.GB11361@arm.com> (raw)
Hi Jean,
I'm getting the following error trying to build perf tool for ARM with
a 3.17-rc6 kernel:
arch/arm/util/unwind-libunwind.c: In function ?libunwind__arch_reg_id?:
arch/arm/util/unwind-libunwind.c:43:3: error: implicit declaration of function ?pr_err? [-Werror=implicit-function-declaration]
pr_err("unwind: invalid reg id %d\n", regnum);
^
arch/arm/util/unwind-libunwind.c:43:3: error: nested extern declaration of ?pr_err? [-Werror=nested-externs]
CC arch/arm/tests/regs_load.o
CC arch/arm/tests/dwarf-unwind.o
cc1: all warnings being treated as errors
Makefile.perf:655: recipe for target 'arch/arm/util/unwind-libunwind.o' failed
make[1]: *** [arch/arm/util/unwind-libunwind.o] Error 1
make[1]: *** Waiting for unfinished jobs....
CC util/probe-finder.o
arch/arm/tests/dwarf-unwind.c: In function ?sample_ustack?:
arch/arm/tests/dwarf-unwind.c:20:3: error: implicit declaration of function ?pr_debug? [-Werror=implicit-function-declaration]
pr_debug("failed to allocate sample uregs data\n");
^
arch/arm/tests/dwarf-unwind.c:20:3: error: nested extern declaration of ?pr_debug? [-Werror=nested-externs]
cc1: all warnings being treated as errors
Makefile.perf:655: recipe for target 'arch/arm/tests/dwarf-unwind.o' failed
make[1]: *** [arch/arm/tests/dwarf-unwind.o] Error 1
Makefile:68: recipe for target 'all' failed
make: *** [all] Error 2
Can you take a look please?
Will
next reply other threads:[~2014-09-26 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 16:25 Will Deacon [this message]
2014-09-26 18:42 ` perf tool failing to build for ARM Jean Pihet
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=20140926162530.GB11361@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).