From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ben Guthro <ben.guthro@gmail.com>,
Ian Munsie <imunsie@au1.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH] perf tool: Fix build for NO_DWARF=1 case
Date: Tue, 2 Oct 2012 18:45:36 -0300 [thread overview]
Message-ID: <20121002214536.GA23354@infradead.org> (raw)
In-Reply-To: <20121002131049.GC6379@krava.brq.redhat.com>
Em Tue, Oct 02, 2012 at 03:10:49PM +0200, Jiri Olsa escreveu:
> On Tue, Oct 02, 2012 at 07:39:23AM -0400, Ben Guthro wrote:
> > 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?
> attached patch fixies the issue for me. Adding Arnaldo to the loop.
[acme@sandy linux]$ make -j8 -C tools/perf/ LIBUNWIND_DIR=/opt/libunwind O=/home/acme/git/build/perf install
cc1: warnings being treated as errors
arch/x86/util/dwarf-regs.c:72: error: no previous prototype for ‘get_arch_regstr’
make: *** [/home/acme/git/build/perf/arch/x86/util/dwarf-regs.o] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/git/linux/tools/perf'
[acme@sandy linux]$
- Arnaldo
next prev parent reply other threads:[~2012-10-02 21:45 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 ` [PATCH] perf tool: Fix build for NO_DWARF=1 case Jiri Olsa
2012-10-02 21:45 ` Arnaldo Carvalho de Melo [this message]
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=20121002214536.GA23354@infradead.org \
--to=acme@redhat.com \
--cc=ben.guthro@gmail.com \
--cc=dsahern@gmail.com \
--cc=imunsie@au1.ibm.com \
--cc=jolsa@redhat.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