Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] perf: add kernel version checks
Date: Tue, 08 Jan 2013 07:41:44 +0100	[thread overview]
Message-ID: <50EBBFA8.1070503@mind.be> (raw)
In-Reply-To: <20130107212531.5E07E9A691@busybox.osuosl.org>

On 07/01/13 21:40, Peter Korsgaard wrote:
> perf is only available since kernel 2.6.31, so if we can't find
> tools/perf/Makefile, error out and tell the user about this.
>
> perf without libelf can only be built since kernel 3.7, so error out
> and tell the user about this if he's trying to build perf from a<  3.7
> kernel without libelf.
>
> Unfortunately, those tests can only be build-time checks as we either
> need to know the real kernel version (i.e, using LINUX_VERSION would
> not be correct as it can be a Git commit ID, or Git tag), or have
> access to the kernel sources themselves. So we can't prevent those
> invalid situations at the configuration, we can only nicely tell the
> user at build time.
>
> Signed-off-by: Thomas Petazzoni<thomas.petazzoni@free-electrons.com>
> Signed-off-by: Peter Korsgaard<jacmet@sunsite.dk>

  There are a number of packages that would benefit from kernel version 
checks. For instance, the native driver implementations of igh-ethercat 
are specific for a certain kernel version. Would it be a good idea to 
make the kernel version user-configurable, and add a check for its 
correctness similar to the external toolchains?

  This would allow us to add a kernel build to the autobuilders, and thus 
autobuild the 5 packages that depend on BR2_LINUX_KERNEL.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-01-08  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 20:40 [Buildroot] [git commit] perf: add kernel version checks Peter Korsgaard
2013-01-08  6:41 ` Arnout Vandecappelle [this message]
2013-01-08  8:15   ` Thomas Petazzoni
2013-01-08  8:28     ` Arnout Vandecappelle
2013-01-08  8:42       ` 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=50EBBFA8.1070503@mind.be \
    --to=arnout@mind.be \
    --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