From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/perf: build outside kernel tree
Date: Thu, 19 Mar 2015 13:21:00 +0200 [thread overview]
Message-ID: <20150319112100.GG2415@tarshish> (raw)
In-Reply-To: <CAKbGBLjn3LqxTxBYUtRK8q8tCPPfto2LJfFcg7Rn5pD6NMN_9Q@mail.gmail.com>
Hi Steven,
On Thu, Mar 19, 2015 at 04:04:38AM -0700, Steven Noonan wrote:
> On Thu, Mar 19, 2015 at 4:02 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Thu, Mar 19, 2015 at 03:57:31AM -0700, Steven Noonan wrote:
> >> # Source taken from the Linux kernel tree
> >> -PERF_SOURCE =
> >> PERF_VERSION = $(call qstrip,$(BR2_LINUX_KERNEL_VERSION))
> >> +PERF_SOURCE = linux-$(PERF_VERSION).tar.xz
> >> +ifeq ($(findstring x2.6.,x$(PERF_VERSION)),x2.6.)
> >> +PERF_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/v2.6
> >> +else
> >> +PERF_SITE = $(BR2_KERNEL_MIRROR)/linux/kernel/v3.x
> >
> > What about v4.x?
>
> Good callout. Have there been related changes submitted for the
> linux-headers and kernel packages?
In case the maintainers decide this is the way to go about perf (which I
doubt), then we should move this code to a common place instead of duplicating
it. While at it we should also fix the v4.x case.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-03-19 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 10:57 [Buildroot] [PATCH v2] package/perf: build outside kernel tree Steven Noonan
2015-03-19 11:02 ` Baruch Siach
2015-03-19 11:04 ` Steven Noonan
2015-03-19 11:21 ` Baruch Siach [this message]
2015-03-19 12:15 ` Thomas Petazzoni
2015-03-19 12:46 ` Steven Noonan
2015-07-11 23:11 ` 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=20150319112100.GG2415@tarshish \
--to=baruch@tkos.co.il \
--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