All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <samoht.yrag@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm] QT4 on i.MX6?
Date: Tue, 14 Jan 2014 13:24:00 -0700	[thread overview]
Message-ID: <52D59CE0.2090306@gmail.com> (raw)
In-Reply-To: <52D54AFD.1000403@gmail.com>

On 2014-01-14 07:34, Gary Thomas wrote:
> On 2014-01-14 06:03, Gary Thomas wrote:
>> On 2014-01-14 05:24, Otavio Salvador wrote:
>>> Hello Gary,
>>>
>>>
>>> On Mon, Jan 13, 2014 at 1:49 PM, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>>>
>>>     When I try to run QT4 (embedded) on my i.MX6 platforms, they
>>>     all crash during initialization.
>>>
>>>     root@sabrelite:~# gdb qtdemoE
>>>     GNU gdb (GDB) 7.6.1
>>>     Copyright (C) 2013 Free Software Foundation, Inc.
>>>     License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.__html <http://gnu.org/licenses/gpl.html>>
>>>     This is free software: you are free to change and redistribute it.
>>>     There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>>>     and "show warranty" for details.
>>>     This GDB was configured as "arm-amltd-linux-gnueabi".
>>>     For bug reporting instructions, please see:
>>>     <http://www.gnu.org/software/__gdb/bugs/ <http://www.gnu.org/software/gdb/bugs/>>...
>>>     Reading symbols from /usr/bin/qtdemoE...(no debugging symbols found)...done.
>>>     (gdb) r -qws
>>>     Starting program: /usr/bin/qtdemoE -qws
>>>     Program received signal SIGSEGV, Segmentation fault.
>>>     gcoOS_InitLocalDisplayInfo (Display=0x0,
>>>          localDisplay=localDisplay@__entry=0x34bc8504) at gc_hal_user_dri.c:3919
>>>     (gdb) bt
>>>     #0  gcoOS_InitLocalDisplayInfo (Display=0x0,
>>>          localDisplay=localDisplay@__entry=0x34bc8504) at gc_hal_user_dri.c:3919
>>>     #1  0x2c46905c in veglInitLocalDisplayInfo (Display=Display@entry=__0x34bc84f8)
>>>          at gc_egl_platform.c:336
>>>     #2  0x2c463240 in veglReferenceDisplay (Thread=Thread@entry=0x5ddf0,
>>>          Display=Display@entry=__0x34bc84f8) at gc_egl_init.c:969
>>>     #3  0x2c4635f8 in eglInitialize (Dpy=0x34bc84f8, major=0x0, minor=0x0)
>>>          at gc_egl_init.c:1185
>>>     #4  0x2b5da3b0 in QEgl::display() () from /usr/lib/libQtGuiE.so.4
>>>     #5  0x2b5dbbe4 in QEgl::chooseConfig(__QEglProperties const*, QEgl::PixelFormatMatch) () from /usr/lib/libQtGuiE.so.4
>>>     #6  0x2b5dc4d8 in QEglContext::chooseConfig(__QEglProperties const&, QEgl::PixelFormatMatch) () from /usr/lib/libQtGuiE.4
>>>     #7  0x2aeb04d4 in QGLContext::chooseContext(__QGLContext const*) ()
>>>         from /usr/lib/libQtOpenGLE.so.4
>>>     #8  0x2ae73ee4 in QGLContext::create(QGLContext const*) ()
>>>         from /usr/lib/libQtOpenGLE.so.4
>>>     #9  0x2aeb01c4 in QGLWidget::setContext(__QGLContext*, QGLContext const*, bool)
>>>          () from /usr/lib/libQtOpenGLE.so.4
>>>     #10 0x2ae74290 in ?? () from /usr/lib/libQtOpenGLE.so.4
>>>
>>>
>>>     Has anyone else tried this on i.MX6 (and got it to work)?
>>>
>>>
>>> Mario (added in Cc) has got same error in one of our customers BSP, he is investigating the issue.
>>>
>>> Mario, it seems the error is because it is using the X11 backend. So please rebuild using:
>>>
>>> DISTRO_FEATURES_remove = "x11 wayland"
>>>
>>> and retest.
>>
>> Sadly, that fails big time :-(
>>
>> ERROR: Nothing PROVIDES 'virtual/libx11' (but /home/local/poky-multi/meta/recipes-multimedia/gstreamer/gst-plugins-base_0.10.36.bb DEPENDS on or otherwise requires it)
>> ERROR: libx11-diet PROVIDES virtual/libx11 but was skipped: missing required distro feature ['x11'] (not in DISTRO_FEATURES)
>> ERROR: libx11 PROVIDES virtual/libx11 but was skipped: missing required distro feature ['x11'] (not in DISTRO_FEATURES)
>> ERROR: nativesdk-libx11 PROVIDES virtual/libx11 but was skipped: missing required distro feature ['x11'] (not in DISTRO_FEATURES)
>> NOTE: Runtime target 'qwt-e' is unbuildable, removing...
>> Missing or unbuildable dependency chain was: ['qwt-e', 'qt4-embedded', 'gst-plugins-base', 'virtual/libx11']
>> ERROR: Required build target 'my-qte-image' has no buildable providers.
>> Missing or unbuildable dependency chain was: ['my-qte-image', 'packagegroup-core-qt4e', 'qwt-e', 'qt4-embedded', 'gst-plugins-base', 'virtual/libx11']
>>
>> I'm not sure why this is the case since the gst-plugins-base recipe
>> uses PKGCONFIG to control this:
>>    PACKAGECONFIG[x11] = "--enable-x --enable-xvideo,--disable-x --disable-xvideo,virtual/libx11 libxv libsm libice"
>>
>
> I've worked past this error (in my distribution layers) and am building
> the QTE image from scratch.  This takes quite a while - I'll report what
> I find when it's complete.

This now works.  I can't tell if it's using the Vivante - the display is
pretty slow...

Also, I get continuous errors/warnings running the demo:
    QWSLock::down(): Invalid argument
    QWSLock::up(): Invalid argument
    QWSLock::up(): Invalid argument
    QWSLock::down(): Invalid argument
        ...

Any ideas about this?

Thanks


  reply	other threads:[~2014-01-14 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 15:49 [meta-fsl-arm] QT4 on i.MX6? Gary Thomas
2014-01-14 12:24 ` Otavio Salvador
2014-01-14 13:03   ` Gary Thomas
2014-01-14 14:34     ` Gary Thomas
2014-01-14 20:24       ` Gary Thomas [this message]
2014-01-14 15:42   ` Mario Domenech Goulart

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=52D59CE0.2090306@gmail.com \
    --to=samoht.yrag@gmail.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.