public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Marco <marco@tampabay.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New Kernel headers vs old Kernel headers
Date: Fri, 30 May 2008 21:59:41 +0200	[thread overview]
Message-ID: <20080530195941.GC5609@1wt.eu> (raw)
In-Reply-To: <4840395A.108@tampabay.rr.com>

On Fri, May 30, 2008 at 01:28:58PM -0400, Marco wrote:
> Hello All,
> 
> I've come across a little discrepancy between the glibc docs and linux
> kernel docs when I was trying to figure out what kernel headers I should
> being using for my cross compiling.  The docs seem to say almost exactly
> the opposite thing.
> 
> For a quick summary: linux docs(headers_install.txt) seem to indicate,
> running glibc compiled against new kernel headers, on an older kernel
> will possibly cause problems.  Where as glib docs(FAQ) indicate glibc
> compiled against new kernel headers, will run fine on an older kernel.
> 
> Can someone shed some light on this (i.e. which is right)?
> 
> Thank you in advance
> 
> Marco Fonseca
> 
> (p.s. I've included the sections from both docs below for easy reference)

IMHO and from experience, the kernel's version is the right one. Also,
it makes some sense, considering that even if you try to run an old
binary on a recent kernel, it generally works while the other way around
is not always true. Note however that what is said in glibc's doc mostly
talks about missing features. They may consider that the glibc offers an
abstraction between the application and the kernel, so that it should be
transparent to the application.

I think the right approach is to base your work on the oldest kernel you
intend to support. That way you'll get most features with the maximum
guarantee of backwards compatibility.

Willy


      reply	other threads:[~2008-05-30 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 17:28 New Kernel headers vs old Kernel headers Marco
2008-05-30 19:59 ` Willy Tarreau [this message]

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=20080530195941.GC5609@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco@tampabay.rr.com \
    /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