All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego <diego.ml@zoho.com>
To: meta-freescale@yoctoproject.org
Subject: Re: 3.10.17-1.0.0_beta meta-fsl-bsp-release layer
Date: Thu, 23 Jan 2014 09:41:19 +0100	[thread overview]
Message-ID: <12768449.LrIj686flz@localhost.localdomain> (raw)
In-Reply-To: <CACoWYqXyc9JQxA4KZbxtjVy_dBg6PJA+-p_pdUEnuUOaAouqEw@mail.gmail.com>

In data mercoledì 22 gennaio 2014 07:41:03, Alok Kumar ha scritto:
> I ran into following errors while building chromium for nitrogen6X, could
> someone advise if something not compatible in my conf layer (below)
> 
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbwin
> dow.cpp:423:51: warning: narrowing conversion of 'XEMBED_VERSION' from
> 'unsigned int' to 'long int' inside { } [-Wnarrowing]
>      long data[] = { XEMBED_VERSION, XEMBED_MAPPED };
>                                                    ^
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbcon
> nection.cpp: In constructor
> 'QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, const char*)':
> /home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-gnueabi/q
> tbase/5.1.1-r0/qtbase-opensource-src-5.1.1/src/plugins/platforms/xcb/qxcbcon
> nection.cpp:275:50: error: cannot convert 'Display* {aka _XDisplay*}' to
> 'EGLNativeDisplayType {aka _FBDisplay*}' for argument '1' to 'void*
> eglGetDisplay(EGLNativeDisplayType)'
>          EGLDisplay eglDisplay = eglGetDisplay(dpy);
>                                                   ^

Hi Alok,

please take a look closely to the error log, because I think you haven't.
/home/user/yocto/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
gnueabi/qtbase/5.1.1-r0/qtbase-opensource-
src-5.1.1/src/plugins/platforms/xcb/qxcbconnection.cpp:275:50:
error: cannot convert 'Display* {aka _XDisplay*}' to 'EGLNativeDisplayType

Can be easily seen is a qtbase 5.1.1 error, not a Chromium error. qtbase is 
not required for Chromium.

Please remove qt related things from your IMAGE_INSTALL_append and try again.

Bests,
Diego



  reply	other threads:[~2014-01-23  8:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 16:08 3.10.17-1.0.0_beta meta-fsl-bsp-release layer Alok Kumar
2014-01-20 16:21 ` Eric Nelson
2014-01-20 16:44   ` Alok Kumar
2014-01-20 20:58     ` Alok Kumar
2014-01-21  3:14     ` Eric Nelson
2014-01-21 14:42       ` Diego
2014-01-21 15:22         ` Booting 3.5.7 kernel on imx6sabresd? randy.krakora
2014-01-21 15:39           ` Otavio Salvador
2014-01-21 16:16             ` randy.krakora
2014-01-21 16:21               ` Otavio Salvador
2014-01-21 20:11                 ` Ra37740@freescale.comndy
2014-01-21 20:23                   ` Otavio Salvador
2014-01-21 21:03                     ` Daiane.Angolini
2014-01-22 15:06                       ` randy.krakora
2014-01-22 15:10                         ` Fabio Estevam
2014-01-22 17:47                           ` randy.krakora
2014-01-22 17:52                             ` Fabio Estevam
2014-01-21 19:25         ` 3.10.17-1.0.0_beta meta-fsl-bsp-release layer Eric Nelson
2014-01-22 12:41           ` Alok Kumar
2014-01-23  8:41             ` Diego [this message]
2014-01-23 11:08               ` Alok Kumar
2014-01-23 15:08       ` Alok Kumar
2014-01-23 15:14         ` Gary Thomas
     [not found]           ` <CACoWYqXYmKAQ3L_9HjLvEEwJNQ56G+9ENcgup7t44D25EpTTcA@mail.gmail.com>
2014-01-23 16:06             ` Gary Thomas
2014-01-23 16:49               ` Alok Kumar
2014-01-24 16:41                 ` Alok Kumar
2014-01-24 16:55                   ` Eric Nelson
2014-01-24 21:30                     ` Otavio Salvador
2014-01-23 15:43         ` Eric Nelson
  -- strict thread matches above, loose matches on Subject: below --
2014-01-22 18:40 alokcherryhills

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=12768449.LrIj686flz@localhost.localdomain \
    --to=diego.ml@zoho.com \
    --cc=meta-freescale@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.