Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Refuse to run bitbake on a kernel that is too old.
Date: Tue, 21 Oct 2014 07:30:41 +0800	[thread overview]
Message-ID: <54459B21.5010403@windriver.com> (raw)
In-Reply-To: <CAJTo0LYQpivPS30fDyXV0mB4AGyM7sY=p2a8D+rYsk51JcWUbQ@mail.gmail.com>

On 10/21/14, 3:08 AM, Burton, Ross wrote:
> On 20 October 2014 19:30,  <jeffrey.honig@windriver.com> wrote:
>> +    # Check that our kernel will work for crosssdk
>> +    if os.uname()[0] == "Linux" and LooseVersion(os.uname()[2]) < LooseVersion(d.getVar('OLDEST_KERNEL')):
>> +        status.addresult("The system requires a kernel of at least %s to run\n" % d.getVar('OLDEST_KERNEL'))
>> +
>
> The OLDEST_KERNEL documentation says:
>
>                      Declares the oldest version of the Linux kernel that the
>                      produced binaries must support.
>                      This variable is passed into the build of the Embedded
>                      GNU C Library (<filename>eglibc</filename>).
>
> So surely checking this value at *runtime in bitbake* isn't correct.

The generated SDK has the same limitation as the runtime since we moved to 
building the SDK for things like the buildtools-tarball.

While it -might- work on older kernels, I think we do need to limit the version 
we support to match the SDK and related, otherwise we will have issues.  (Do we 
also need to add this to the SDK .sh installer script?  probably.)

--Mark

> Ross
>



  reply	other threads:[~2014-10-20 23:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 18:30 [PATCH] Refuse to run bitbake on a kernel that is too old jeffrey.honig
2014-10-20 19:08 ` Burton, Ross
2014-10-20 23:30   ` Mark Hatle [this message]
2014-10-21 10:03 ` Enrico Scholz
2014-10-22 10:49   ` Mark Hatle

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=54459B21.5010403@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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