From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11776] qt5webengine 5.12.2 build failed with arm toolchain and linaro toolchain
Date: Sat, 05 Oct 2019 18:14:21 +0000 [thread overview]
Message-ID: <bug-11776-163-3LGvTEIatl@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11776-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11776
--- Comment #4 from Bernd Kuhls <bernd.kuhls@t-online.de> ---
(In reply to fazibear from comment #2)
Today I hit this bug with buildroot master (37be55a5db) and this defconfig:
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_BINUTILS_VERSION_2_32_X=y
BR2_GCC_VERSION_9_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_DRI_DRIVER_I965=y
BR2_PACKAGE_MESA3D_OPENGL_GLX=y
BR2_PACKAGE_MESA3D_OPENGL_EGL=y
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5WEBENGINE=y
BR2_PACKAGE_XORG7=y
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-10-05 18:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 9:04 [Buildroot] [Bug 11776] New: qt5webengine 5.12.2 build failed with arm toolchain and linaro toolchain bugzilla at busybox.net
2019-06-10 12:53 ` Nathan Ford
2019-06-11 1:21 ` Nathan Ford
2019-06-17 20:34 ` David Barbion
2019-06-18 13:41 ` Nathan Ford
2019-06-18 14:14 ` David Barbion
2019-06-22 12:50 ` Nathan Ford
2019-06-22 13:50 ` Nathan Ford
2019-06-22 17:29 ` Nathan Ford
2019-06-22 18:48 ` Nathan Ford
2019-06-25 20:55 ` Arnout Vandecappelle
2019-06-26 18:33 ` Michał Kalbarczyk
2019-06-27 21:45 ` Nathan Ford
2019-06-28 10:12 ` Michał Kalbarczyk
2019-07-04 16:32 ` Michał Kalbarczyk
2019-06-19 12:02 ` [Buildroot] [Bug 11776] " bugzilla at busybox.net
2019-06-19 20:20 ` bugzilla at busybox.net
2019-06-20 20:48 ` David Barbion
2019-10-03 8:48 ` bugzilla at busybox.net
2019-10-05 18:14 ` bugzilla at busybox.net [this message]
2022-09-18 10:52 ` bugzilla
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=bug-11776-163-3LGvTEIatl@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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