From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: add defconfig for Freescale i.MX31 PDK
Date: Thu, 19 Mar 2015 16:58:44 +0100 [thread overview]
Message-ID: <20150319165844.63a1fe52@free-electrons.com> (raw)
In-Reply-To: <550AED3F.4070606@freescale.com>
Dear Vincent Stehl?,
On Thu, 19 Mar 2015 16:37:35 +0100, Vincent Stehl? wrote:
> >> +BR2_KERNEL_HEADERS_3_2=y
> > That doesn't sound like a good idea when the kernel is 2.6.28...
>
> Granted, this is not optimal. Those are the kernel headers
> closest to 2.6.28, "easily" available in buildroot.
>
> It is indeed possible to manually specify the 2.6.28 kernel
> headers version, but this necessitates two patches to fix the
> linux-headers "build".
> Do you prefer this solution?
It is not a preference at all: running userspace binaries and C
libraries built with kernel headers more recent than the running is a
very good recipe for disaster. Your userspace and C library will
believe that certain system calls exist while it's not the case.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-19 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 9:43 [Buildroot] [PATCH] configs: add defconfig for Freescale i.MX31 PDK Vincent Stehlé
2015-03-18 23:32 ` Arnout Vandecappelle
2015-03-19 15:37 ` Vincent Stehlé
2015-03-19 15:58 ` Thomas Petazzoni [this message]
2015-03-19 21:26 ` Arnout Vandecappelle
2015-03-19 21:28 ` Arnout Vandecappelle
2015-03-20 14:53 ` Vincent Stehlé
2015-03-20 14:57 ` [Buildroot] [PATCH v4] " Vincent Stehlé
2015-03-21 17:27 ` Arnout Vandecappelle
2015-03-24 18:51 ` Vincent Stehlé
2015-03-24 18:53 ` [Buildroot] [PATCH v5] " Vincent Stehlé
2015-03-25 0:02 ` Thomas Petazzoni
2015-03-19 15:52 ` [Buildroot] [PATCH v2] " Vincent Stehlé
2015-03-19 21:32 ` Arnout Vandecappelle
2015-03-20 9:02 ` Vincent Stehlé
2015-03-20 9:05 ` [Buildroot] [PATCH v3] " Vincent Stehlé
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=20150319165844.63a1fe52@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.