From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH 1/1] gst-fsl-plugins: fix compile for sysroot based on newer linux kernel headers
Date: Sat, 19 Apr 2014 23:56:39 +0200 [thread overview]
Message-ID: <20140419235639.14dec5f6@skate> (raw)
In-Reply-To: <20140304225057.0d010df6@skate>
Arnout,
On Tue, 4 Mar 2014 22:50:57 +0100, Thomas Petazzoni wrote:
> > Maybe a generic solution for packages that require specific kernel
> > headers is to include a headers_install in the kernel's build?
>
> But will it work properly? I mean, most of the time, the packages that
> need this are vendor-specific packages, that want to access specific
> definitions in vendor-specific kernels. And the quality of
> vendor-specific kernels is usually quite low, so there are quite some
> chances that headers_install might not necessarily do the right thing
> as it will not have been properly tested...
>
> > Anyway, for this one, if it works with -I with all our external
> > toolchains and with an internal uClibc and glibc toolchain, then I guess
> > it's OK. Perhaps something got fixed in the gst-fsl-plugins bump.
>
> Is this a Acked-by for the patch?
Ping ? :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-19 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 22:18 [Buildroot] [RFC/PATCH 0/1] gst-fsl-plugins: fix compile for sysroot based on newer linux kernel headers Peter Seiderer
2014-02-25 22:18 ` [Buildroot] [RFC/PATCH 1/1] " Peter Seiderer
2014-03-02 8:48 ` Thomas Petazzoni
2014-03-04 17:40 ` Arnout Vandecappelle
2014-03-04 21:50 ` Thomas Petazzoni
2014-04-19 21:56 ` Thomas Petazzoni [this message]
2014-10-06 15:18 ` Thomas Petazzoni
2014-02-25 22:28 ` [Buildroot] [RFC/PATCH 0/1] " Peter Korsgaard
2014-02-25 22:53 ` Peter Seiderer
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=20140419235639.14dec5f6@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