From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung.kim@lge.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] perf symbols: Implement poor man's ELF parser
Date: Tue, 22 May 2012 09:52:58 +0200 [thread overview]
Message-ID: <1337673178.9698.0.camel@twins> (raw)
In-Reply-To: <20120521114739.GC5923@m.brq.redhat.com>
On Mon, 2012-05-21 at 13:47 +0200, Jiri Olsa wrote:
> I can see all this exported in:
>
> [jolsa@dhcp-26-214 perf]$ rpm -qf /usr/include/elf.h
> glibc-headers-2.14.90-24.fc16.6.x86_64
>
> so maybe we dont need to add our own, since glic-headers
> seems crutial anyway ;)
There's people building perf against uclibc and such, not sure they
carry it.
next prev parent reply other threads:[~2012-05-22 7:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 7:10 [RFC 0/5] perf tools: Minimalistic build without libelf dependency Namhyung Kim
2012-05-14 7:10 ` [PATCH 1/5] perf symbols: Introduce symbol__elf_init() Namhyung Kim
2012-05-14 7:10 ` [PATCH 2/5] perf symbols: Do not use ELF's symbol binding constants Namhyung Kim
2012-05-14 7:10 ` [PATCH 3/5] perf tools: Split out util/symbol-elf.c Namhyung Kim
2012-05-21 11:45 ` Jiri Olsa
2012-05-22 1:00 ` Namhyung Kim
2012-05-22 8:35 ` Jiri Olsa
2012-05-14 7:10 ` [PATCH 4/5] perf tools: Support minimal build Namhyung Kim
2012-05-14 7:10 ` [PATCH 5/5] perf symbols: Implement poor man's ELF parser Namhyung Kim
2012-05-21 11:47 ` Jiri Olsa
2012-05-22 1:08 ` Namhyung Kim
2012-05-22 7:52 ` Peter Zijlstra [this message]
2012-05-22 10:26 ` Namhyung Kim
2012-05-22 10:44 ` Peter Zijlstra
2012-05-14 9:22 ` [RFC 0/5] perf tools: Minimalistic build without libelf dependency Ingo Molnar
2012-05-15 0:40 ` Namhyung Kim
2012-05-21 6:00 ` Namhyung Kim
2012-05-21 15:03 ` David Ahern
2012-05-22 0:20 ` 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=1337673178.9698.0.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung.kim@lge.com \
--cc=namhyung@gmail.com \
--cc=paulus@samba.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.