From: Jiri Olsa <jolsa@redhat.com>
To: Ben Guthro <ben.guthro@gmail.com>
Cc: Ian Munsie <imunsie@au1.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung.kim@lge.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH] perf tool: Fix build for NO_DWARF=1 case
Date: Tue, 2 Oct 2012 15:10:49 +0200 [thread overview]
Message-ID: <20121002131049.GC6379@krava.brq.redhat.com> (raw)
In-Reply-To: <CAOvdn6VELd9vPGyptmeBePsNsnQNtgXdgj4bYRfuLyz0cXsD9w@mail.gmail.com>
On Tue, Oct 02, 2012 at 07:39:23AM -0400, Ben Guthro wrote:
> Hi Ian,
>
> Once again - apologies for multiple copies of this email. Please reply
> to this (plain text) version so it will get through LKML filters.
>
> On Tue, Oct 2, 2012 at 12:24 AM, Ian Munsie <imunsie@au1.ibm.com> wrote:
> >
> >
> > > CC arch/x86/util/dwarf-regs.o
> >
> > Is this correct? i.e. Are you building perf for x86?
>
> Yes, x86_64, specifically.
>
> >
> > What commandline are you using to build?
>
> cd /data/home/bguthro/dev/orc-newdev.git/linux/build/tools/tools/perf
> && make EXTRAVERSION=-orc
>
> >
> > Any exported environment variables that may be relevant?
>
> none that I can think of.
>
> >
> > What dev libraries does perf warn is missing (Is libdw-dev among them)?
>
> make[3]: Entering directory
> `/data/home/bguthro/dev/orc-newdev.git/linux/build/tools/tools/perf'
> Makefile:502: No libunwind found, disabling post unwind support.
> Please install libunwind-dev[el] >= 0.99
> Makefile:537: No libdw.h found or old libdw.h found or elfutils is
> older than 0.138, disables dwarf support. Please install new
> elfutils-devel/libdw-dev
> Makefile:567: No libaudit.h found, disables 'trace' tool, please
> install audit-libs-devel or libaudit-dev
> Makefile:580: newt not found, disables TUI support. Please install
> newt-devel or libnewt-dev
> Makefile:752: No bfd.h/libbfd found, install
> binutils-dev[el]/zlib-static to gain symbol demangling
>
> Actually - I hadn't noticed these warnings before.
>
> After installing libdw-dev - the perf build completed successfully.
> Perhaps this should be fatal, rather than a warning?
>
> Thanks for your help
>
> Ben
hi,
attached patch fixies the issue for me. Adding Arnaldo to the loop.
jirka
---
We need to include arch Makefile after we decide the NO_DWARF value,
otherwise we get might get build failure.
The reason is the arch Makefile could include objects based on
the NO_DWARF value, as it is for x86 case.
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: Jiri Olsa <jolsa@redhat.com>
---
tools/perf/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/Makefile b/tools/perf/Makefile
index 6958ba4..0ca8f45 100644
--- a/tools/perf/Makefile
+++ b/tools/perf/Makefile
@@ -505,8 +505,6 @@ ifneq ($(call try-cc,$(SOURCE_LIBUNWIND),$(FLAGS_UNWIND)),y)
endif # Libunwind support
endif # NO_LIBUNWIND
--include arch/$(ARCH)/Makefile
-
ifneq ($(OUTPUT),)
BASIC_CFLAGS += -I$(OUTPUT)
endif
@@ -635,6 +633,8 @@ else
endif
endif
+-include arch/$(ARCH)/Makefile
+
disable-python = $(eval $(disable-python_code))
define disable-python_code
BASIC_CFLAGS += -DNO_LIBPYTHON
--
1.7.11.4
next prev parent reply other threads:[~2012-10-02 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOvdn6WPUDqYPpHZip7dxVVXJXT0-zJOUCpgDGb=o+zqq98F0Q@mail.gmail.com>
2012-10-02 4:24 ` linux-next: build failure in dwarf-regs.c Ian Munsie
2012-10-02 11:39 ` Ben Guthro
2012-10-02 13:10 ` Jiri Olsa [this message]
2012-10-02 21:45 ` [PATCH] perf tool: Fix build for NO_DWARF=1 case Arnaldo Carvalho de Melo
2012-10-03 10:29 ` Jiri Olsa
2012-10-03 13:29 ` Namhyung Kim
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=20121002131049.GC6379@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=ben.guthro@gmail.com \
--cc=dsahern@gmail.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung.kim@lge.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
all inboxes | Powered by JetHome®