Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] 2009.11-rc1 build failure
Date: Fri, 27 Nov 2009 04:47:09 -0600	[thread overview]
Message-ID: <200911270447.11916.minimod@morethan.org> (raw)
In-Reply-To: <87eink70bd.fsf@macbook.be.48ers.dk>

On Fri November 27 2009, Peter Korsgaard wrote:
> 
> Notice that your kernel headers version doesn't need to be the same as
> the kernel version you're using.
> 
- - - -
>
> I don't know about PXA in particular (but even if so, please use the
> latest in the 2.6.27.x series). In general, the latest stable kernel
> release (currently 2.6.31.6) is the most sensible choice.
> 

Although a newcomer to using Buildroot -
the above is not Buildroot specific advice -
It is a good rule of thumb when building for Linux.

For example (my current use case):

I am building user land code against the 2.6.31.6 *headers*
even though that code will be running on a 2.6.12.6 kernel
released Aug. 29, 2005. (At least until I replace it.)

That is an amazing level of backwards compatibility.
Of course, it allows a person to build code today that uses
system calls that might not exist at run-time. ;)
But in cases like that, your userland code will get an error,
not break something.

On the other hand, I can see your case for wanting to build
against the oldest, stable (I.E: still supported) kernel.
Which is 2.6.27.x, most recently released version Nov. 10, 2009.
Doing that might avoid some of those run-time surprises.  ;)

So it probably depends on your own project goals -
Greatest degree of compatibility now (2.6.27.x), or
longest lasting compatibility going forwarded (2.6.31.x).

I am shooting for "rebuild userland every 5 years" myself. ;)

Mike

  reply	other threads:[~2009-11-27 10:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 14:15 [Buildroot] 2009.11-rc1 build failure Joachim Pihl
2009-11-26 14:31 ` Peter Korsgaard
2009-11-27  8:03   ` Joachim Pihl
2009-11-27 10:02     ` Peter Korsgaard
2009-11-27 10:47       ` Michael S. Zick [this message]
2009-11-27 18:09       ` Joachim Pihl
     [not found]       ` <op.u32e97xjyqa4qb@jap-lappis>
2009-11-27 18:13         ` Peter Korsgaard
2009-11-27 18:26           ` Michael S. Zick
2009-11-27 18:41           ` Joachim Pihl
2009-11-27 18:51             ` Peter Korsgaard
2009-11-27 19:11               ` Joachim Pihl
2009-11-27 19:42                 ` Peter Korsgaard

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=200911270447.11916.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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