Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] perf: new package
Date: Thu, 03 Jan 2013 17:48:45 +0200	[thread overview]
Message-ID: <50E5A85D.5050102@petroprogram.com> (raw)
In-Reply-To: <50E5A2B4.6090405@petroprogram.com>

3.1.2013 17:24, Stefan Fr?berg kirjoitti:
> 3.1.2013 17:07, Thomas Petazzoni kirjoitti:
>> This patch adds a new package that allows to build the 'perf'
>> userspace tool that comes in the tools/perf directory of the kernel
>> sources.
>>
>> It is an alternative proposal to the one done by Kaiwan Billimoria
>> <kaiwan.billimoria@gmail.com>, in that it creates the package in
>> package/perf/. It therefore properly integrates with the Buildroot
>> package infrastructure.
>>
>> Of course, the package depends on the Linux kernel to be built by
>> Buildroot, in order to get Perf sources matching the version of the
>> kernel that will be executed.
>>
>> One remaining issue is that this package only builds properly with
>> kernel >= v3.7 (but it was the same with Kaiwan proposal) : the
>> NO_LIBELF variable, which allows to get rid of the libelf dependency,
>> has only been introduced between 3.6 and 3.7. If we want to support
>> older kernel versions, we'll have to create a package for libelf.
> Here is an elfutils 0.155 (which contains libelf) for buildroot that I
> posted some time ago.
> Patch #4 is missing from that list because it was too big to submit to
> this list.
>
> http://lists.busybox.net/pipermail/buildroot/2012-December/063855.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063856.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063864.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063858.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063857.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063859.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063861.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063860.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063863.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063862.html
> http://lists.busybox.net/pipermail/buildroot/2012-December/063865.html
>
> Regards
> Stefan
>


And now while i *still* remember, that first patch, patch #1 should be
replaced with this

http://lists.busybox.net/pipermail/buildroot/2012-December/063876.html

> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2013-01-03 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 15:07 [Buildroot] [PATCH] perf: new package Thomas Petazzoni
2013-01-03 15:24 ` Stefan Fröberg
2013-01-03 15:48   ` Stefan Fröberg [this message]
2013-01-03 23:22   ` Thomas Petazzoni
2013-01-04 14:01     ` Stefan Fröberg
2013-01-04 14:25     ` Stefan Fröberg
2013-01-04 14:27       ` Thomas Petazzoni
2013-01-04  6:05 ` Kaiwan Billimoria
2013-01-04  8:22   ` Thomas Petazzoni

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=50E5A85D.5050102@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --cc=buildroot@busybox.net \
    /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