From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11341] Compiling qt5base-5.11.1 with libressl results in many 'was not declared in this scope' errors
Date: Thu, 15 Aug 2019 14:32:44 +0000 [thread overview]
Message-ID: <bug-11341-163-84C71mx8JA@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11341-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11341
--- Comment #5 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Peter: building Qt5 (latest) with LibreSSL still fails, I can reproduce with
the current master and the following defconfig:
BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2019.05.1.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_4_9=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_14=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_QT5=y
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_LIBRESSL=y
BR2_PACKAGE_PCRE=y
BR2_PACKAGE_PCRE_16=y
BR2_PACKAGE_PCRE_UTF=y
# BR2_TARGET_ROOTFS_TAR is not set
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-15 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 14:10 [Buildroot] [Bug 11341] New: Compiling qt5base-5.11.1 with libressl results in many 'was not declared in this scope' errors bugzilla at busybox.net
2018-09-11 19:53 ` [Buildroot] [Bug 11341] " bugzilla at busybox.net
2018-09-11 20:07 ` bugzilla at busybox.net
2018-11-02 9:51 ` bugzilla at busybox.net
2018-11-02 14:55 ` bugzilla at busybox.net
2019-08-15 14:32 ` bugzilla at busybox.net [this message]
2024-06-15 14:48 ` 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-11341-163-84C71mx8JA@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