From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] QtWebEngine on RPI 0 W
Date: Thu, 20 Feb 2020 23:56:41 +0100 [thread overview]
Message-ID: <20200220235641.1b8be4c1@gmx.net> (raw)
In-Reply-To: <20200218145224.3f449bac@gmx.net>
Hello Rafa,
On Tue, 18 Feb 2020 14:52:24 +0100, Peter Seiderer <ps.report@gmx.net> wrote:
> Hello Rafa,
>
> On Wed, 5 Feb 2020 07:20:39 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:
>
> > > Hi again,
> > >
> > > I have tested the QtWebEngine with a qt example and I got:
> > >
> > > # ./minimal -platform eglfs
> > > Illegal instruction
> > >
> > > Any idea of what could be causing it?
> > >
> > >Hard to say without further information..., did your compile
> > >minimal yourself or did you enable 'BR2_PACKAGE_QT5BASE_EXAMPLES=y'
> > >and used the one installed as
> > '/usr/lib/qt/examples/webenginewidgets/minimal/minimal'
> > >on the target?
> >
> > I had enabled 'BR2_PACKAGE_QT5BASE_EXAMPLES=y' and I have used the one in
> > '/usr/lib/qt/examples/webenginewidgets/minimal/minimal'
> >
> > Result of 'file minimal':
> >
> > minimal: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically
> > linked, interpreter /lib/ld-, for GNU/Linux 4.19.0, stripped
> >
> > I have no problems running other samples like the qtvirtualkeyboard or touch
> > ones
> >
> >
> > >Please provide a complete .config (or defconfig) file...
> >
> > Here my defconfig: cp4_defconfig.cp4_defconfig
> > <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>
> >
> >
> > >Still using buildroot-2019.02.09?
> >
> > Yes
>
> I can confirm your crash/illegal instruction with the provided config
> using minimal example on RPi0 (it crashes somewhere in the static
> constructors)...
And finally found the root cause of the problem, the qtwebengine configure step
determines the wrong compile flags for the chromium build system, simple
using some (wrong) ARMv7 arm defaults instead ARMv6 for the rpi zero...
A proof-of-concept patch sent to the mailing list, see [1]...
With the patch applied I can start qtwebengine examples minimal
and quicknanobrowser...
Regards,
Peter
[1] https://patchwork.ozlabs.org/patch/1241702/
>
> Regards,
> Peter
>
> >
> > >Regards,
> > >Peter
> >
> > Kind Regards,
> >
> > Rafa
> >
> >
> >
> >
> > --
> > Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2020-02-20 22:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 10:21 [Buildroot] QtWebEngine on RPI 0 W rscr
2020-01-25 16:25 ` Peter Seiderer
2020-01-28 7:41 ` rscr
2020-01-28 7:58 ` Peter Seiderer
2020-01-28 9:43 ` Peter Seiderer
2020-01-30 11:38 ` rscr
2020-01-30 12:02 ` Peter Seiderer
2020-01-30 12:20 ` Peter Seiderer
2020-02-03 12:51 ` rscr
2020-02-05 11:34 ` rscr
2020-02-05 13:12 ` Peter Seiderer
2020-02-05 13:20 ` rscr
2020-02-05 14:25 ` rscr
2020-02-18 13:52 ` Peter Seiderer
2020-02-20 22:56 ` Peter Seiderer [this message]
2020-02-24 12:21 ` rscr
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=20200220235641.1b8be4c1@gmx.net \
--to=ps.report@gmx.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