From: rscr <rafacrespiramon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] QtWebEngine on RPI 0 W
Date: Tue, 28 Jan 2020 01:41:07 -0600 (CST) [thread overview]
Message-ID: <1580197267384-0.post@n4.nabble.com> (raw)
In-Reply-To: <20200125172550.45366ce5@gmx.net>
> 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/
next prev parent reply other threads:[~2020-01-28 7:41 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 [this message]
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
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=1580197267384-0.post@n4.nabble.com \
--to=rafacrespiramon@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.