All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] QT5.8 buid failure on master
Date: Tue, 7 Mar 2017 14:16:49 -0300	[thread overview]
Message-ID: <CAOMZO5DMPYsXzftVtW_-Mv5PbK2h_=3atnQNku9ed6uxgw_ACg@mail.gmail.com> (raw)
In-Reply-To: <CAD6G_RSPtn=Mta0sW67Ay8eAfHnvJ+tQ-pTMwJ1s6v_0Q24wzA@mail.gmail.com>

On Tue, Mar 7, 2017 at 2:11 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> On Tue, Mar 7, 2017 at 10:27 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Jagan,
>>
>> On Tue, Mar 7, 2017 at 1:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>
>>> Able to see the application but 'Black screen' on 'Lord of the Ring' widget
>>
>> Thanks for testing.
>>
>> I think we should treat this issue on a separate thread as I also see
>> the same with Qt5.6.2.
>
> OK, so we need to investigate framebuffer issue? do you have any suggestions.

If I understand correctly the same 4.9.13 kernel that you use with
Gary's rootfs is able to launch the Qt5 Cinematic just fine, right?

So we need to understand what changed from Gary's rootfs compared to
master that caused the regression.

  reply	other threads:[~2017-03-07 17:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 22:41 [Buildroot] QT5.8 buid failure on master Fabio Estevam
2017-03-07  7:33 ` Peter Seiderer
2017-03-07 11:48   ` Gary Bisson
2017-03-07 12:15     ` Jagan Teki
2017-03-07 14:04     ` Peter Seiderer
2017-03-07 16:15       ` Jagan Teki
2017-03-07 16:32         ` Jagan Teki
2017-03-07 16:57         ` Fabio Estevam
2017-03-07 17:11           ` Jagan Teki
2017-03-07 17:16             ` Fabio Estevam [this message]
2017-03-07 17:19               ` Jagan Teki
2017-03-07 19:29           ` Peter Seiderer
2017-03-08 10:45             ` Gary Bisson
2017-03-08 11:00               ` Jagan Teki
2017-03-08 11:28                 ` Gary Bisson
2017-03-08 12:19                   ` Jagan Teki
2017-03-12 22:43               ` Fabio Estevam

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='CAOMZO5DMPYsXzftVtW_-Mv5PbK2h_=3atnQNku9ed6uxgw_ACg@mail.gmail.com' \
    --to=festevam@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 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.