From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Marti Raudsepp <marti@juffo.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: add compatibility with libelf 0.8 and autodetect
Date: Fri, 23 Oct 2009 19:56:18 -0200 [thread overview]
Message-ID: <193b0f820910231456o24bf95b6mf3e72f1b27870af5@mail.gmail.com> (raw)
In-Reply-To: <20091023210231.GC8356@elte.hu>
(sorry, Ingo, forgot to reply-all)
On Fri, Oct 23, 2009 at 19:02, Ingo Molnar <mingo@elte.hu> wrote:
> Also, this would be an urgent fix for v2.6.32 too, to make perf build on
> Arch Linux, agreed?
>
If the fix is as simple as this patch, and will not cause any other
problems, may it be sent to -stable as well?
To make perf build on Arch is also possible to install elfutils from
AUR (http://aur.archlinux.org/packages.php?ID=5300) and I've made a
request some months ago to switch to this library instead of using
libelf but got no answers.
I think it's Arch's fault to continue using an unmaintained library
when there's an easy replacement, but if the "fix" is easy, why not?
Lucas De Marchi
next prev parent reply other threads:[~2009-10-23 21:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 20:37 Marti Raudsepp
2009-10-23 21:02 ` Ingo Molnar
2009-10-23 21:48 ` Marti Raudsepp
2009-10-23 21:52 ` Ingo Molnar
2009-10-23 22:10 ` Marti Raudsepp
2009-10-24 1:07 ` Lucas De Marchi
2009-10-24 1:18 ` Marti Raudsepp
2009-10-24 8:30 ` Ingo Molnar
2009-10-24 13:26 ` Lucas De Marchi
2009-10-24 15:13 ` Marti Raudsepp
2009-10-24 15:19 ` Marti Raudsepp
2009-10-24 15:41 ` Ingo Molnar
2009-10-24 16:10 ` Marti Raudsepp
2009-10-23 21:56 ` Lucas De Marchi [this message]
2009-10-23 21:59 ` Marti Raudsepp
2009-10-23 22:16 ` Lucas De Marchi
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=193b0f820910231456o24bf95b6mf3e72f1b27870af5@mail.gmail.com \
--to=lucas.de.marchi@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=arjan@linux.intel.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marti@juffo.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®