[Buildroot] Latest stable Buildroot version 2019.05.1 - qt5webengine builderror
Patrick Koller
koller at stettbacher.ch
Wed Aug 21 13:10:42 UTC 2019
Hi buildroot team :)
I am using the latest stable Buildroot version 2019.05.1, but I am
facing a builderror with the qt5webengine and I hope, that someone could
help me out with this issue.
My setup:
From a hardware point of view, I am using a Ka-Ro TX6QP
computer-on-module with an i.mx6 (ARM Cortex-A9) processor. For this
reason, I am using the Linaro ARM 2018.05 toolchain (Proposed by
Buildroot 2019.05.1). The goal is to build the qt5webengine (Latest:
Qt5.12.2) successfully.
The challenge, I am facing right now:
I wanted to build the qt5webengine, but I got several error messages in
this style:
> /home/patrickk/tmp/buildroot/buildroot-2019.05.1/buildroot-2019.05.1/output/host/opt/ext-toolchain/arm-linux-gnueabihf/include/c++/7.3.1/cstdlib:75:15:
> fatal error: stdlib.h: No such file or directory
> #include_next <stdlib.h>
> ^~~~~~~~~~
> compilation terminated.
A quick google search (https://bugreports.qt.io/browse/QTBUG-53367)
showed a known problem with new GCC > 4.8 versions in respect of the
argument "-isystem". Nevertheless, I was not able to solve my described
problem at the source.
Next, I tried to update the linaro toolchain to the newest available
version, but the same error showed off...
Link:
https://releases.linaro.org/components/toolchain/binaries/7.4-2019.02/arm-linux-gnueabihf/gcc-linaro-7.4.1-2019.02-x86_64_arm-linux-gnueabihf.tar.xz
My last attempt was to update Qt5 to version 5.13.0. This showed the
following error:
> In file included from
> ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_parameters_restrictions.cc:25:0:
> ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_parameters_restrictions.cc:
> In function ‘sandbox::bpf_dsl::ResultExpr sandbox::RestrictPtrace()’:
> ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/syscall_parameters_restrictions.cc:401:9:
> error: ‘PTRACE_GET_THREAD_AREA’ was not declared in this scope
> PTRACE_GET_THREAD_AREA,
> ^
I am not sure, if my update from Qt5.12..2 to Qt5.13.0 solved the first
error or even introduced a second error...
It would be awesome, if someone could help me out or give me a hint. I
appreciate every support I get :)
I attached my .config file to this e-mail. If you need additional
information, please do not hesitate to contact me.
Thanks in advance.
Best regards
Patrick
===================================================
Stettbacher Signal Processing
Patrick Koller
Office:
Neugutstrasse 54
CH-8600 Dübendorf - Switzerland
Phone +41 - 43 299 57 23
Web: www.stettbacher.ch
===================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/x-config
Size: 107152 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190821/672f7f42/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linaro_arm_2018.05_qt5.12.2_error.log
Type: text/x-log
Size: 33586 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190821/672f7f42/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linaro_arm_2018.05_qt5.13.0_error.log
Type: text/x-log
Size: 20740 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190821/672f7f42/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linaro_arm_2019.02_qt5.12.2_error.log
Type: text/x-log
Size: 27417 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190821/672f7f42/attachment-0007.bin>
More information about the buildroot
mailing list