From: Gary Bisson <bisson.gary@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gst-fsl-plugins: fix includes for recent toolchains
Date: Thu, 24 Jul 2014 23:42:16 -0700 [thread overview]
Message-ID: <1406270536-17145-1-git-send-email-bisson.gary@gmail.com> (raw)
Build was failing starting with CodeSourcery 2013.11 due to
new v4l kernel headers.
Signed-off-by: Gary Bisson <bisson.gary@gmail.com>
---
Yann, all,
I know this patch will look bad as we already discussed the use of -I instead of -idirafter.
However it has been reported and verified that this package doesn't build using recent toolchain such as CodeSourcery 2013.11.
It seems to come from the fact that the kernel headers in the toolchain have been updated which brings some incompatibility.
Using -idirafter, the v4l header picked up is from the toolchain which is missing some older structures like v4l2_dbg_chip_ident.
The CPPFLAGS setup is now exactly the same as what is done in Yocto.
Let me know your thoughts.
Thanks,
Gary
---
package/gstreamer/gst-fsl-plugins/gst-fsl-plugins.mk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/gstreamer/gst-fsl-plugins/gst-fsl-plugins.mk b/package/gstreamer/gst-fsl-plugins/gst-fsl-plugins.mk
index 1ae6596..b441233 100644
--- a/package/gstreamer/gst-fsl-plugins/gst-fsl-plugins.mk
+++ b/package/gstreamer/gst-fsl-plugins/gst-fsl-plugins.mk
@@ -24,7 +24,8 @@ GST_FSL_PLUGINS_CONF_ENV = \
# needs access to imx-specific kernel headers
GST_FSL_PLUGINS_DEPENDENCIES += linux
-GST_FSL_PLUGINS_CONF_ENV += CPPFLAGS="$(TARGET_CPPFLAGS) -idirafter $(LINUX_DIR)/include/uapi"
+GST_FSL_PLUGINS_CONF_ENV += \
+ CPPFLAGS="-I$(LINUX_DIR)/include/uapi -I$(LINUX_DIR)/include"
ifeq ($(BR2_PACKAGE_XLIB_LIBX11),y)
GST_FSL_PLUGINS_DEPENDENCIES += xlib_libX11
--
2.0.1
next reply other threads:[~2014-07-25 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 6:42 Gary Bisson [this message]
2014-07-25 16:40 ` [Buildroot] [PATCH] gst-fsl-plugins: fix includes for recent toolchains Yann E. MORIN
2014-07-25 17:51 ` Gary Bisson
2014-07-25 20:38 ` Yann E. MORIN
2014-07-26 7:34 ` Thomas Petazzoni
2014-07-26 17:06 ` Gary Bisson
2014-07-26 17:13 ` Yann E. MORIN
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=1406270536-17145-1-git-send-email-bisson.gary@gmail.com \
--to=bisson.gary@gmail.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