From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf fails to compile for latest Linus tree
Date: Wed, 13 Mar 2013 13:58:50 -0600 [thread overview]
Message-ID: <5140DA7A.1030405@gmail.com> (raw)
In-Reply-To: <20130313195656.GG11779@ghostprotocols.net>
On 3/13/13 1:56 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Mar 13, 2013 at 08:50:35AM -0600, David Ahern escreveu:
>> I believe this has been fixed but I don't see it in your tree
>> (perf/core or perf/urgent) or in the tip tree:
>
>> builtin-annotate.c: In function ‘hists__find_annotations’:
>> builtin-annotate.c:161:4: error: duplicate case value
>> builtin-annotate.c:154:4: error: previously used here
>> make: *** [/tmp/pbuild/builtin-annotate.o] Error 1
>> make: *** Waiting for unfinished jobs....
>
> Yeah, this is because you don't have newt-devel installed, please try
> with acme/perf/urgent after two patches from Michael Ellerman appear at
> its head, I just pushed it.
right. minimal F18 install. I don't have python-config installed either
which makes perf unhappy. Have to add PYTHON_CONFIG=/bin/false to get it
to work. Can't figure out the logic to have it test for the executable.
David
prev parent reply other threads:[~2013-03-13 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 14:50 perf fails to compile for latest Linus tree David Ahern
2013-03-13 19:56 ` Arnaldo Carvalho de Melo
2013-03-13 19:58 ` David Ahern [this message]
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=5140DA7A.1030405@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.