From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] perf tools: Can't find util/unwind.h
Date: Sat, 11 Aug 2012 15:16:41 -0300 [thread overview]
Message-ID: <20120811181641.GC3503@infradead.org> (raw)
In-Reply-To: <87ipcpbkvy.fsf@kernel.org>
Em Sat, Aug 11, 2012 at 10:47:45PM +0900, Namhyung Kim escreveu:
> Hi Arnaldo,
>
> Your current perf/core branch fails to build like this:
>
> $ make
> Makefile:494: No libunwind found. Please install libunwind >= 0.99
> CC perf.o
> make: *** No rule to make target `util/unwind.h', needed by `builtin-annotate.o'. Stop.
>
> $ ls util/unwind*
> ls: cannot access util/unwind*: No such file or directory
>
> Forgot to add the files?
yeah, did some manual fixlets and forgot to add some files, since I
hadn't yet asked Ingo to pull I took the liberty of fixing it up and
force push the result, sorry about that, 'git rebase' should be fine to
get back on track.
Thanks for reporting!
- Arnaldo
prev parent reply other threads:[~2012-08-11 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 13:47 [BUG] perf tools: Can't find util/unwind.h Namhyung Kim
2012-08-11 18:16 ` Arnaldo Carvalho de Melo [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=20120811181641.GC3503@infradead.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox