From: Denys Dmytriyenko <denys@ti.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: meta-ti mailing list <meta-ti@yoctoproject.org>
Subject: Re: omap3-sgx-modules fails on do_compile
Date: Tue, 24 Jun 2014 19:04:43 -0400 [thread overview]
Message-ID: <20140624230443.GP6700@edge> (raw)
In-Reply-To: <CAMCfZKH23Ow_q1MQPi3Hu3oGjTGqpJ=CyO5kXYXoK3uoE-55qA@mail.gmail.com>
Graphics SDK 5.01.01.01 doesn't work with kernel 3.14 yet.
The last tested kernel version to work with Graphics SDK was 3.12; and 3.14
has changed some APIs, hence the breakage.
--
Denys
On Tue, Jun 24, 2014 at 06:04:52PM -0300, Diego Sueiro wrote:
> Folks,
>
> I'm using both yocto and meta-ti on daisy branch and removed meta-yocto-bsp
> from bblayers.conf.
>
> Doing a bitbake omap3-sgx-modules I'm receiving the following error:
>
>
> DEBUG: Executing shell function do_compile
> NOTE: make -j 8 -e MAKEFLAGS=
> KERNEL_PATH=/<snip>/build-daisy/tmp-eglibc/sysroots/beaglebone/usr/src/kernel
> KERNEL_SRC=/<snip>/build-daisy/tmp-eglibc/sysroots/beaglebone/usr/src/kernel
> KERNEL_VERSION=3.14.8 CC=arm-qubit-linux-gnueabi-gcc -mno-thumb-interwork
> -marm LD=arm-qubit-linux-gnueabi-ld.bfd AR=arm-qubit-linux-gnueabi-ar
> BUILD=release TI_PLATFORM=ti335x SUPPORT_XORG=
> make -C /<snip>/build-daisy/tmp-eglibc/sysroots/beaglebone/usr/src/kernel
> M=`pwd`
> make[1]: Entering directory
> `/<snip>/build-daisy/tmp-eglibc/sysroots/beaglebone/usr/src/kernel'
> CC [M]
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.o
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:
> In function 'OMAPLFBWaitForVSync':
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:7:
> error: implicit declaration of function 'register_vsync_cb'
> [-Werror=implicit-function-declaration]
> if (register_vsync_cb((vsync_callback_t)grpx_irq_wait_handler,
> &completion, psDevInfo->uiFBDevID) != 0)
> ^
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:30:
> error: 'vsync_callback_t' undeclared (first use in this function)
> if (register_vsync_cb((vsync_callback_t)grpx_irq_wait_handler,
> &completion, psDevInfo->uiFBDevID) != 0)
> ^
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:30:
> note: each undeclared identifier is reported only once for each function it
> appears in
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:710:47:
> error: expected ')' before 'grpx_irq_wait_handler'
> if (register_vsync_cb((vsync_callback_t)grpx_irq_wait_handler,
> &completion, psDevInfo->uiFBDevID) != 0)
> ^
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:716:7:
> error: implicit declaration of function 'unregister_vsync_cb'
> [-Werror=implicit-function-declaration]
> if (unregister_vsync_cb((vsync_callback_t)grpx_irq_wait_handler ,
> &completion, psDevInfo->uiFBDevID) != 0)
> ^
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.c:716:49:
> error: expected ')' before 'grpx_irq_wait_handler'
> if (unregister_vsync_cb((vsync_callback_t)grpx_irq_wait_handler ,
> &completion, psDevInfo->uiFBDevID) != 0)
> ^
> cc1: some warnings being treated as errors
> make[3]: ***
> [/<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux/omaplfb_linux.o]
> Error 1
> make[2]: ***
> [/<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM/services4/3rdparty/dc_ti335x_linux]
> Error 2
> make[1]: ***
> [_module_/<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/Graphics_SDK_5_01_01_01/GFX_Linux_KM]
> Error 2
> make[1]: Leaving directory
> `/<snip>/build-daisy/tmp-eglibc/sysroots/beaglebone/usr/src/kernel'
> make: *** [all] Error 2
> ERROR: oe_runmake failed
> WARNING: exit code 1 from a shell command.
> ERROR: Function failed: do_compile (log file is located at
> /<snip>/build-daisy/tmp-eglibc/work/beaglebone-qubit-linux-gnueabi/omap3-sgx-modules/5.01.01.01-r22a/temp/log.do_compile.3405)
>
> I'm I missing something?
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>
> /*long live rock 'n roll*/
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2014-06-24 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 21:04 omap3-sgx-modules fails on do_compile Diego Sueiro
2014-06-24 23:04 ` Denys Dmytriyenko [this message]
2014-06-25 12:41 ` Diego Sueiro
2014-06-25 14:11 ` Denys Dmytriyenko
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=20140624230443.GP6700@edge \
--to=denys@ti.com \
--cc=diego.sueiro@gmail.com \
--cc=meta-ti@yoctoproject.org \
/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.