Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] media-ctl build failure (autobuild)
Date: Thu, 28 Mar 2013 09:53:08 +0100	[thread overview]
Message-ID: <20130328095308.4fac9fcf@skate> (raw)
In-Reply-To: <CAAXf6LUxBkO6-g-dHs8_2cagNFiBYAWCE3KAEcuT=zWEsJdZMA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Thu, 28 Mar 2013 08:44:54 +0100, Thomas De Schampheleire wrote:

> What is the appropriate action here:
> 1. remove the old toolchains?
> 2. add some kind of fragile dependency between media-ctl and specific
> toolchain config variables
> 3. introduce a way to specify which kernel header versions are used for
> external toolchains, and check this for packages that need it
> 4. don't bother, let the package fail for these old toolchains

5. Do what I've done for neard, i.e
package/neard/neard-fix-missing-linux-nfc-header.patch: we add a
patch to the package that integrates directly into the package the
required kernel headers, and adjust the autoconf script to either use
the header from the toolchain if it's available, or the bundled header
if not. Over time, toolchains will be updated to more recent kernel
header versions, and we should be able to get rid of such patches.

Even though it's not really nice, I believe it's the least painful way.

Of course, it has the drawback that if the user happens to use a kernel
version that does not have the NFC functionality of the media-ctl
functionality, it will simply not work.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-03-28  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  7:44 [Buildroot] media-ctl build failure (autobuild) Thomas De Schampheleire
2013-03-28  8:53 ` Thomas Petazzoni [this message]
2013-04-02 19:44   ` Thomas De Schampheleire

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=20130328095308.4fac9fcf@skate \
    --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