From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9121] gst1-imx for i.MX6 compile failed, cannot find PXP, IPU and other errors
Date: Mon, 01 Aug 2016 08:48:30 +0000 [thread overview]
Message-ID: <bug-9121-163-4BBXpe1ino@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9121-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9121
--- Comment #4 from Gary Bisson <gary.bisson@boundarydevices.com> ---
Hi,
Actually your log states it uses the rel_imx_3.14.52_1.1.0_ga tag.
Can you list the content of the following folder?
/home/ganhx/work/buildroot/qt5-buildroot/mx6output/build/linux-rel_imx_3.14.52_1.1.0_ga/include
What is strange is that the headers from the git repo are here as expected:
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/include/linux/ipu.h?id=rel_imx_3.14.52_1.1.0_ga
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/include/linux/pxp_device.h?id=rel_imx_3.14.52_1.1.0_ga
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/include/uapi/linux/v4l2-controls.h?id=rel_imx_3.14.52_1.1.0_ga
Regards,
Gary
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-08-01 8:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 1:06 [Buildroot] [Bug 9121] New: gst1-imx for i.MX6 compile failed, cannot find PXP, IPU and other errors bugzilla at busybox.net
2016-08-01 1:10 ` [Buildroot] [Bug 9121] " bugzilla at busybox.net
2016-08-01 1:59 ` bugzilla at busybox.net
2016-08-01 8:36 ` bugzilla at busybox.net
2016-08-01 8:48 ` bugzilla at busybox.net [this message]
2016-08-02 1:11 ` bugzilla at busybox.net
2016-08-02 1:23 ` bugzilla at busybox.net
2016-08-02 9:51 ` bugzilla at busybox.net
2016-08-02 22:37 ` bugzilla at busybox.net
2016-08-03 0:54 ` bugzilla at busybox.net
2016-08-04 10:05 ` bugzilla at busybox.net
2016-08-31 1:39 ` bugzilla at busybox.net
2016-08-31 6:14 ` bugzilla at busybox.net
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=bug-9121-163-4BBXpe1ino@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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