From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain support improvements
Date: Mon, 3 Nov 2008 09:31:10 +0100 [thread overview]
Message-ID: <20081103093110.13e43438@surf> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909C2916F@mi8nycmail19.Mi8.com>
Le Fri, 31 Oct 2008 14:42:14 -0400,
"hartleys" <hartleys@visionengravers.com> a ?crit :
> What are the side effects if you use an external toolchain that was
> built with a given kernel version, say 2.6.20.4, but use a newer
> kernel, say 2.6.27.3?
The kernel <-> userspace interface is backward compatible. So if you
use a toolchain that was compiled against the headers of kernel
2.6.20.4 and run the binaries under 2.6.27.3, them it will work
perfectly fine. The only thing is that you won't be able to use the new
system calls, data structures, headers, defines, that have been added
in the kernel between 2.6.20.4 and 2.6.27.3.
The reverse side: if you generate binaries with a toolchain that has
been compiled against the headers of kernel 2.6.27.3 and run it on a
2.6.20.4 kernel, then there are two cases :
* You don't use any of the new features of the kernel <-> userspace
interface added between 2.6.20.4 and 2.6.27.3 : everything will work
correctly ;
* You use one of these new features: your binary might fail to run
properly (for example if they use a new system call, that isn't
available in your kernel).
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2008-11-03 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 8:45 [Buildroot] External toolchain support improvements Thomas Petazzoni
2008-10-31 18:42 ` hartleys
2008-11-03 8:31 ` Thomas Petazzoni [this message]
2008-11-03 15:52 ` hartleys
2008-11-03 23:51 ` Markus Heidelberg
2008-10-31 19:21 ` Grant Likely
2008-11-03 10:15 ` Peter Korsgaard
2008-11-03 10:18 ` Peter Korsgaard
2008-11-03 12:48 ` Shinya Kuribayashi
2008-11-03 12:58 ` Peter Korsgaard
2008-11-03 13:25 ` Shinya Kuribayashi
2008-11-03 14:03 ` 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=20081103093110.13e43438@surf \
--to=thomas.petazzoni@free-electrons.com \
--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