[Buildroot] QtWebEngine on RPI 0 W

[Buildroot] QtWebEngine on RPI 0 W

[rscr]

Hi, 

I have built a custom image for RPI 0 W. Now I need QT with QtWebEngine. 

- As I am using  toolchain *arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf*, I
have to use Qt 5.6.3 because it is supported by GCC > 4.8

ISSUE:

When trying to build the image, I got building failed. Some of the errors
are:

Running configuration tests (phase 1)...
/home/ibercomp/rcr/projects/cp4/buildroot/output/host/bin/arm-linux-gnueabihf-g++
-c -fvisibility=hidden fvisibility.c
Symbol visibility control enabled.
collect2: fatal error: cannot find 'ld'
compilation terminated
...
Makefile:192: recipe for target 'db2.o' failed
...
Makefile:192: recipe for target 'ibase.o' failed
...
Makefile:195: recipe for target 'icu.o' failed
make[2]: *** [icu.o] Error 1
ICU disabled.
The ICU library support cannot be enabled.


Find attached my defconfig: cp4_defconfig.cp4_defconfig
<http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>  

*Any idea of what I've been missing?*

It is possible having Qt 5.11.3 and once built the image, add a QtWebEngine
version supported by my gcc?  

Kind Regards, 

Rafa





--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] QtWebEngine on RPI 0 W

[Peter Seiderer]

On Fri, 24 Jan 2020 04:21:10 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Hi,
>
> I have built a custom image for RPI 0 W. Now I need QT with QtWebEngine.
>
> - As I am using  toolchain *arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf*, I
> have to use Qt 5.6.3 because it is supported by GCC > 4.8

Why stay with this old-gcc-version toolchain?

>
> ISSUE:
>
> When trying to build the image, I got building failed. Some of the errors
> are:
>
> Running configuration tests (phase 1)...
> /home/ibercomp/rcr/projects/cp4/buildroot/output/host/bin/arm-linux-gnueabihf-g++
> -c -fvisibility=hidden fvisibility.c
> Symbol visibility control enabled.
> collect2: fatal error: cannot find 'ld'
> compilation terminated
> ...
> Makefile:192: recipe for target 'db2.o' failed
> ...
> Makefile:192: recipe for target 'ibase.o' failed
> ...
> Makefile:195: recipe for target 'icu.o' failed
> make[2]: *** [icu.o] Error 1
> ICU disabled.
> The ICU library support cannot be enabled.
>
>
> Find attached my defconfig: cp4_defconfig.cp4_defconfig
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>

Important information missing, which buildroot version do you use?

Please provide a more complete failure output (one where can be seen which package is failing),
see e.g. a random autobuild failure [1] for example....

Regards,
Peter

[1]  http://autobuild.buildroot.net/results/03d7f4c955f55b4d15b51b55c8e779cfaf25c089/build-end.log

>
> *Any idea of what I've been missing?*
>
> It is possible having Qt 5.11.3 and once built the image, add a QtWebEngine
> version supported by my gcc?
>
> 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] QtWebEngine on RPI 0 W

[rscr]

> Hi,
>
> I have built a custom image for RPI 0 W. Now I need QT with QtWebEngine.
>
> - As I am using  toolchain *arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf*, I
> have to use Qt 5.6.3 because it is supported by GCC > 4.8
>
>Why stay with this old-gcc-version toolchain?

- This toolchain is the one recommended in raspberry/tools github: 
https://github.com/raspberrypi/tools/blob/master/arm-bcm2708/arm-linux-gnueabihf
<https://github.com/raspberrypi/tools/blob/master/arm-bcm2708/arm-linux-gnueabihf>  

If there is a new version, I didn't know it. I could use, for example, these
toolchains? https://github.com/abhiTronix/raspberry-pi-cross-compilers
<https://github.com/abhiTronix/raspberry-pi-cross-compilers>  

>
> ISSUE:
>
> When trying to build the image, I got building failed. Some of the errors
> are:
>
> Running configuration tests (phase 1)...
> /home/ibercomp/rcr/projects/cp4/buildroot/output/host/bin/arm-linux-gnueabihf-g++
> -c -fvisibility=hidden fvisibility.c
> Symbol visibility control enabled.
> collect2: fatal error: cannot find 'ld'
> compilation terminated
> ...
> Makefile:192: recipe for target 'db2.o' failed
> ...
> Makefile:192: recipe for target 'ibase.o' failed
> ...
> Makefile:195: recipe for target 'icu.o' failed
> make[2]: *** [icu.o] Error 1
> ICU disabled.
> The ICU library support cannot be enabled.
>
>
> Find attached my defconfig: cp4_defconfig.cp4_defconfig
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>
>
>Important information missing, which buildroot version do you use?

I am using buildroot-2019.02.09

I will build the image again to provide the complete failure output....but
If there is any solution where I could keep using QT 5.11.3 version with a
GCC > 5 I prefer it.

Kind Regards, 

Rafa









--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] QtWebEngine on RPI 0 W

[Peter Seiderer]

Hello Rafa,

On Tue, 28 Jan 2020 01:41:07 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> > Hi,
> >
> > I have built a custom image for RPI 0 W. Now I need QT with QtWebEngine.
> >
> > - As I am using  toolchain *arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf*, I
> > have to use Qt 5.6.3 because it is supported by GCC > 4.8
> >
> >Why stay with this old-gcc-version toolchain?
>
> - This toolchain is the one recommended in raspberry/tools github:
> https://github.com/raspberrypi/tools/blob/master/arm-bcm2708/arm-linux-gnueabihf
> <https://github.com/raspberrypi/tools/blob/master/arm-bcm2708/arm-linux-gnueabihf>
>
> If there is a new version, I didn't know it. I could use, for example, these
> toolchains? https://github.com/abhiTronix/raspberry-pi-cross-compilers
> <https://github.com/abhiTronix/raspberry-pi-cross-compilers>
>

Use an up-to-date buildroot generated one (downside is an increased build duration) ;-)

> >
> > ISSUE:
> >
> > When trying to build the image, I got building failed. Some of the errors
> > are:
> >
> > Running configuration tests (phase 1)...
> > /home/ibercomp/rcr/projects/cp4/buildroot/output/host/bin/arm-linux-gnueabihf-g++
> > -c -fvisibility=hidden fvisibility.c
> > Symbol visibility control enabled.
> > collect2: fatal error: cannot find 'ld'
> > compilation terminated
> > ...
> > Makefile:192: recipe for target 'db2.o' failed
> > ...
> > Makefile:192: recipe for target 'ibase.o' failed
> > ...
> > Makefile:195: recipe for target 'icu.o' failed
> > make[2]: *** [icu.o] Error 1
> > ICU disabled.
> > The ICU library support cannot be enabled.
> >
> >
> > Find attached my defconfig: cp4_defconfig.cp4_defconfig
> > <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>
> >
> >Important information missing, which buildroot version do you use?
>
> I am using buildroot-2019.02.09
>
> I will build the image again to provide the complete failure output....but
> If there is any solution where I could keep using QT 5.11.3 version with a
> GCC > 5 I prefer it.

Thanks for the info, will try to reproduce your failure (did try it with
buildroot-2019.11.1 but qt5webengine-5.6.3 compile failed because of
incompatibility with some of the version bumped dependent libs e.g.
ffmpeg, libjpeg, ...).

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] QtWebEngine on RPI 0 W

[Peter Seiderer]

Hello Rafa,

On Tue, 28 Jan 2020 08:58:28 +0100, Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Rafa,
>
> On Tue, 28 Jan 2020 01:41:07 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:
>
> > > Hi,
> > >
> > > I have built a custom image for RPI 0 W. Now I need QT with QtWebEngine.
> > >
> > > - As I am using  toolchain *arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf*, I
> > > have to use Qt 5.6.3 because it is supported by GCC > 4.8
> > >
> > >Why stay with this old-gcc-version toolchain?
> >
> > - This toolchain is the one recommended in raspberry/tools github:
> > https://github.com/raspberrypi/tools/blob/master/arm-bcm2708/arm-linux-gnueabihf
> > <https://github.com/raspberrypi/tools/blob/master/arm-bcm2708/arm-linux-gnueabihf>
> >
> > If there is a new version, I didn't know it. I could use, for example, these
> > toolchains? https://github.com/abhiTronix/raspberry-pi-cross-compilers
> > <https://github.com/abhiTronix/raspberry-pi-cross-compilers>
> >
>
> Use an up-to-date buildroot generated one (downside is an increased build duration) ;-)
>
> > >
> > > ISSUE:
> > >
> > > When trying to build the image, I got building failed. Some of the errors
> > > are:
> > >
> > > Running configuration tests (phase 1)...
> > > /home/ibercomp/rcr/projects/cp4/buildroot/output/host/bin/arm-linux-gnueabihf-g++
> > > -c -fvisibility=hidden fvisibility.c
> > > Symbol visibility control enabled.
> > > collect2: fatal error: cannot find 'ld'
> > > compilation terminated
> > > ...
> > > Makefile:192: recipe for target 'db2.o' failed
> > > ...
> > > Makefile:192: recipe for target 'ibase.o' failed
> > > ...
> > > Makefile:195: recipe for target 'icu.o' failed
> > > make[2]: *** [icu.o] Error 1
> > > ICU disabled.
> > > The ICU library support cannot be enabled.
> > >
> > >
> > > Find attached my defconfig: cp4_defconfig.cp4_defconfig
> > > <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>
> > >
> > >Important information missing, which buildroot version do you use?
> >
> > I am using buildroot-2019.02.09
> >
> > I will build the image again to provide the complete failure output....but
> > If there is any solution where I could keep using QT 5.11.3 version with a
> > GCC > 5 I prefer it.
>
> Thanks for the info, will try to reproduce your failure (did try it with
> buildroot-2019.11.1 but qt5webengine-5.6.3 compile failed because of
> incompatibility with some of the version bumped dependent libs e.g.
> ffmpeg, libjpeg, ...).

Your given failure maybe irrelevant or your are missing the real failure later on
(or it is a problem with your build host/setup)...

The only failure I get with your defconfig is while compiling
build/qt5webengine-5.6.3/src/3rdparty/chromium/ui/gfx/codec/jpeg_codec.cc,
which can be fixed by the suggested buildroot-2019.02.9 patch (see [1]).

With this patch applied qt5webengine-5.6.3 builds fine here...

Regards,
Peter

[1] https://patchwork.ozlabs.org/patch/1230245

>
> 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

[Buildroot] QtWebEngine on RPI 0 W

[rscr]

Dear Peter, 

Thanks for testing it. As I would like to keep using the Qt 5.11.3. I would
like to find a solution with a gcc toolchain > 5 (webengine requirement)

- Using the one provided by RPI is not possible because it is 4.9.3
- Next I tried to use the buildroot toolchain, with gcc 5 (find attached my
defconfig). 

cp4_defconfig.cp4_defconfig
<http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>  

Now it fails building qt5webengine, when:

./../../3rdparty/chromium/third_party/WebKit/Source/modules/indexeddb/InspectorIndexedDBAgent.cpp:1007:7:
warning: ?blink::ClearObjectStore? has a base
?blink::{anonymous}::ExecutableWithDatabase<blink::protocol::IndexedDB::Backend::ClearObjectStoreCallback>?
whose type uses the anonymous namespace
[15206/15243] CXX obj/QtWebEngineCore/media_capture_devices_dispatcher.o
FAILED: obj/QtWebEngineCore/media_capture_devices_dispatcher.o 

....

virtual memory exhausted: Cannot allocate memory
[15208/15243] CXX obj/QtWebEngineCore/network_delegate_qt.o
ninja: build stopped: subcommand failed.
Makefile.gn_run:331: recipe for target 'run_ninja' failed
make[5]: *** [run_ninja] Error 1
Makefile:80: recipe for target 'sub-gn_run-pro-make_first' failed
make[4]: *** [sub-gn_run-pro-make_first] Error 2
Makefile:77: recipe for target 'sub-core-make_first' failed
make[3]: *** [sub-core-make_first] Error 2
Makefile:46: recipe for target 'sub-src-make_first' failed
make[2]: *** [sub-src-make_first] Error 2
package/pkg-generic.mk:238: recipe for target
'/home/ibercomp/rcr/projects/cp4/buildroot/output/build/qt5webengine-5.11.3/.stamp_built'
failed
make[1]: ***
[/home/ibercomp/rcr/projects/cp4/buildroot/output/build/qt5webengine-5.11.3/.stamp_built]
Error 2
Makefile:84: recipe for target '_all' failed
make: *** [_all] Error 2

This is a problem of the defconfig? The rpi 0 W maybe can not support the
qt5WebEngine? It is a problem with host (I am using Ubuntu 16.04)?

Kind Regards and thanks!

Rafa






--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] QtWebEngine on RPI 0 W

[Peter Seiderer]

Hello Rafa,

On Thu, 30 Jan 2020 05:38:49 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Dear Peter, 
> 
> Thanks for testing it. As I would like to keep using the Qt 5.11.3. I would
> like to find a solution with a gcc toolchain > 5 (webengine requirement)
> 
> - Using the one provided by RPI is not possible because it is 4.9.3
> - Next I tried to use the buildroot toolchain, with gcc 5 (find attached my
> defconfig). 
> 
> cp4_defconfig.cp4_defconfig
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>  
> 
> Now it fails building qt5webengine, when:
> 
> ./../../3rdparty/chromium/third_party/WebKit/Source/modules/indexeddb/InspectorIndexedDBAgent.cpp:1007:7:
> warning: ?blink::ClearObjectStore? has a base
> ?blink::{anonymous}::ExecutableWithDatabase<blink::protocol::IndexedDB::Backend::ClearObjectStoreCallback>?
> whose type uses the anonymous namespace
> [15206/15243] CXX obj/QtWebEngineCore/media_capture_devices_dispatcher.o
> FAILED: obj/QtWebEngineCore/media_capture_devices_dispatcher.o 
> 
> ....
> 
> virtual memory exhausted: Cannot allocate memory

Try to add more RAM to your build host (or swap space) ;-), or
set BR2_JLEVEL (Build options ---> Number of jobs to run simultaneously
(0 for auto)) to an appropriate value...

Regards,
Peter

> [15208/15243] CXX obj/QtWebEngineCore/network_delegate_qt.o
> ninja: build stopped: subcommand failed.
> Makefile.gn_run:331: recipe for target 'run_ninja' failed
> make[5]: *** [run_ninja] Error 1
> Makefile:80: recipe for target 'sub-gn_run-pro-make_first' failed
> make[4]: *** [sub-gn_run-pro-make_first] Error 2
> Makefile:77: recipe for target 'sub-core-make_first' failed
> make[3]: *** [sub-core-make_first] Error 2
> Makefile:46: recipe for target 'sub-src-make_first' failed
> make[2]: *** [sub-src-make_first] Error 2
> package/pkg-generic.mk:238: recipe for target
> '/home/ibercomp/rcr/projects/cp4/buildroot/output/build/qt5webengine-5.11.3/.stamp_built'
> failed
> make[1]: ***
> [/home/ibercomp/rcr/projects/cp4/buildroot/output/build/qt5webengine-5.11.3/.stamp_built]
> Error 2
> Makefile:84: recipe for target '_all' failed
> make: *** [_all] Error 2
> 
> This is a problem of the defconfig? The rpi 0 W maybe can not support the
> qt5WebEngine? It is a problem with host (I am using Ubuntu 16.04)?
> 
> Kind Regards and thanks!
> 
> 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] QtWebEngine on RPI 0 W

[Peter Seiderer]

Hello Rafa,

On Thu, 30 Jan 2020 05:38:49 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Dear Peter, 
> 
> Thanks for testing it. As I would like to keep using the Qt 5.11.3. I would
> like to find a solution with a gcc toolchain > 5 (webengine requirement)
> 
> - Using the one provided by RPI is not possible because it is 4.9.3
> - Next I tried to use the buildroot toolchain, with gcc 5 (find attached my
> defconfig). 
> 
> cp4_defconfig.cp4_defconfig
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/cp4_defconfig.cp4_defconfig>  

Your provided defconfig states:

BR2_TOOLCHAIN_EXTERNAL_PATH="/home/ibercomp/rcr/tools/toolchains/sourceforge/rpi0w/cross-pi-gcc-6.3.0-0"

So you are still not using a buildroot provided toolchain (I suspect from the path your use
one from the https://sourceforge.net/projects/raspberry-pi-cross-compilers/ project)?

BR2_PACKAGE_QT5WEBENGINE is not enabled in the given defconfig, wrong defconfig?

Regards,
Peter

> 
> Now it fails building qt5webengine, when:
> 
> ./../../3rdparty/chromium/third_party/WebKit/Source/modules/indexeddb/InspectorIndexedDBAgent.cpp:1007:7:
> warning: ?blink::ClearObjectStore? has a base
> ?blink::{anonymous}::ExecutableWithDatabase<blink::protocol::IndexedDB::Backend::ClearObjectStoreCallback>?
> whose type uses the anonymous namespace
> [15206/15243] CXX obj/QtWebEngineCore/media_capture_devices_dispatcher.o
> FAILED: obj/QtWebEngineCore/media_capture_devices_dispatcher.o 
> 
> ....
> 
> virtual memory exhausted: Cannot allocate memory
> [15208/15243] CXX obj/QtWebEngineCore/network_delegate_qt.o
> ninja: build stopped: subcommand failed.
> Makefile.gn_run:331: recipe for target 'run_ninja' failed
> make[5]: *** [run_ninja] Error 1
> Makefile:80: recipe for target 'sub-gn_run-pro-make_first' failed
> make[4]: *** [sub-gn_run-pro-make_first] Error 2
> Makefile:77: recipe for target 'sub-core-make_first' failed
> make[3]: *** [sub-core-make_first] Error 2
> Makefile:46: recipe for target 'sub-src-make_first' failed
> make[2]: *** [sub-src-make_first] Error 2
> package/pkg-generic.mk:238: recipe for target
> '/home/ibercomp/rcr/projects/cp4/buildroot/output/build/qt5webengine-5.11.3/.stamp_built'
> failed
> make[1]: ***
> [/home/ibercomp/rcr/projects/cp4/buildroot/output/build/qt5webengine-5.11.3/.stamp_built]
> Error 2
> Makefile:84: recipe for target '_all' failed
> make: *** [_all] Error 2
> 
> This is a problem of the defconfig? The rpi 0 W maybe can not support the
> qt5WebEngine? It is a problem with host (I am using Ubuntu 16.04)?
> 
> Kind Regards and thanks!
> 
> 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] QtWebEngine on RPI 0 W

[rscr]

Dear Peter, 

I have fixed the issue:

- Using the buildroot toolchain with gcc 5.x
- Increasing swap in my Ubuntu host until 10 GB
(https://chromium.googlesource.com/chromium/src/+/master/docs/linux/build_instructions.md#System-requirements) 
- Using BR2_JLEVEL = 2

Now QtWebEngine is built with the image. 

I just have to test if I can run a Qt app with WebEngineView


>Your provided defconfig states:
>
>BR2_TOOLCHAIN_EXTERNAL_PATH="/home/ibercomp/rcr/tools/toolchains/sourceforge/rpi0w/cross-pi-gcc->6.3.0-0"
>
>So you are still not using a buildroot provided toolchain (I suspect from
the path your use
<one from the https://sourceforge.net/projects/raspberry-pi-cross-compilers/
project)?

On the meanwhile, I was trying with some other toolchain because of the
&quot;Virtual exahusted memory&quot; failure I got with the buildroot one.


>BR2_PACKAGE_QT5WEBENGINE is not enabled in the given defconfig, wrong
defconfig?

At first attempt of building an image with a new toolchain, I decided not to
add the QtWebEngine. I just was trying to test if the new toolchain was
worked...and did not.

Kind Regards, 

Rafa







--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] QtWebEngine on RPI 0 W

[rscr]

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?

Kind Regards

Rafa



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] QtWebEngine on RPI 0 W

[Peter Seiderer]

Hello Rafa,

On Wed, 5 Feb 2020 05:34:22 -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?

Please provide a complete .config (or defconfig) file...

Still using buildroot-2019.02.09?

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] QtWebEngine on RPI 0 W

[rscr]

> 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

>Regards,
>Peter

Kind Regards, 

Rafa




--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] QtWebEngine on RPI 0 W

[rscr]

Sorry, 

I am using the one in /usr/lib/qt/examples/*webengine*/minimal/minimal

Kind Regards



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

[Buildroot] QtWebEngine on RPI 0 W

[Peter Seiderer]

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)...

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] QtWebEngine on RPI 0 W

[Peter Seiderer]

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

[Buildroot] QtWebEngine on RPI 0 W

[rscr]

Thanks Peter, 

I will try it

Kind Regards, 

Rafa



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/