public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco <marco@tampabay.rr.com>
To: linux-kernel@vger.kernel.org
Subject: New Kernel headers vs old Kernel headers
Date: Fri, 30 May 2008 13:28:58 -0400	[thread overview]
Message-ID: <4840395A.108@tampabay.rr.com> (raw)

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)


In linux-2.6.24/Documentation/make/headers_install.txt:
...
Kernel headers are backwards compatible, but not forwards compatible.  This
means that a program built against a C library using older kernel headers
should run on a newer kernel (although it may not have access to new
features), but a program built against newer kernel headers may not work
on an
older kernel.
...
------------------
In glibc-2.7/FAQ
...
1.8.    What version of the Linux kernel headers should be used?

{AJ,UD} The headers from the most recent Linux kernel should be used.  The
headers used while compiling the GNU C library and the kernel binary used
when using the library do not need to match.  The GNU C library runs without
problems on kernels that are older than the kernel headers used.  The other
way round (compiling the GNU C library with old kernel headers and running
on a recent kernel) does not necessarily work.  For example you can't use
new kernel features if you used old kernel headers to compile the GNU C
library.
...


             reply	other threads:[~2008-05-30 17:29 UTC|newest]

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

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=4840395A.108@tampabay.rr.com \
    --to=marco@tampabay.rr.com \
    --cc=linux-kernel@vger.kernel.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