From: Peter Zijlstra <peterz@infradead.org>
To: Roland McGrath <roland@redhat.com>
Cc: Masami Hiramatsu <mhiramat@redhat.com>,
Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>, Mike Galbraith <efault@gmx.de>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [PATCH -tip v3 5/9] perf probe: Use elfutils-libdw for analyzing debuginfo
Date: Tue, 23 Feb 2010 21:00:00 -0000 [thread overview]
Message-ID: <1266958809.11845.817.camel@laptop> (raw)
In-Reply-To: <20100223204933.F0A9164C@magilla.sf.frob.com>
On Tue, 2010-02-23 at 12:49 -0800, Roland McGrath wrote:
> > + BASIC_CFLAGS += -I/usr/include/elfutils
>
> The normal method is to use:
>
> #include <elfutils/libdw.h>
>
> Note that <dwarf.h> and <libelf.h> are not in the subdirectory.
We've had funny issues with distro's being inconsistent in placing those
files, so we chose this route of a direct include and playing games with
the include path to make it work.
next prev parent reply other threads:[~2010-02-23 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 2:04 [PATCH -tip v3 0/9] perf-probe updates - use elfutils and introduce lazy matching Masami Hiramatsu
2010-02-23 2:04 ` [PATCH -tip v3 2/9] perf probe: Update perf probe document Masami Hiramatsu
2010-02-23 2:04 ` [PATCH -tip v3 1/9] perf probe: Do not show --line option without dwarf support Masami Hiramatsu
2010-02-23 2:04 ` [PATCH -tip v3 4/9] perf probe: Rename probe finder functions Masami Hiramatsu
2010-02-23 2:04 ` [PATCH -tip v3 3/9] perf probe: Fix bugs in line range finder Masami Hiramatsu
2010-02-23 2:05 ` [PATCH -tip v3 5/9] perf probe: Use elfutils-libdw for analyzing debuginfo Masami Hiramatsu
2010-02-23 20:49 ` Roland McGrath
2010-02-23 21:00 ` Peter Zijlstra [this message]
2010-02-23 2:05 ` [PATCH -tip v3 7/9] perf probe: Check function address range strictly in line finder Masami Hiramatsu
2010-02-23 2:05 ` [PATCH -tip v3 8/9] perf probe: show more lines after last line Masami Hiramatsu
2010-02-23 2:05 ` [PATCH -tip v3 9/9] perf probe: Add lazy line matching support Masami Hiramatsu
2010-02-23 2:05 ` [PATCH -tip v3 6/9] perf probe: Use libdw callback routines Masami Hiramatsu
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=1266958809.11845.817.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=drepper@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).