From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12906] qt PrefixPath is wrong on 2020.05-rc1
Date: Sat, 16 May 2020 16:38:28 +0000 [thread overview]
Message-ID: <bug-12906-163-DfksbfyoAh@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12906-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12906
--- Comment #3 from Peter Seiderer <ps.report@gmx.net> ---
No custom changes (see provided defconfig)...
$ cat build/qt5base-5.14.2/config.summary
Building on: linux-g++ (x86_64, CPU features: mmx sse sse2)
Building for: devices/linux-buildroot-g++ (arm, CPU features: neon crc32)
Target compiler: gcc 8.4.0
Configuration: cross_compile compile_examples enable_new_dtags largefile neon
shared shared release c++11 c++14 c++1z concurrent reduce_exports release_tools
stl
Build options:
Mode ................................... release; optimized tools
Optimize release build for size ........ no
Building shared libraries .............. yes
Using C standard ....................... C11
Using C++ standard ..................... C++17
Using ccache ........................... no
Using new DTAGS ........................ yes
Relocatable ............................ yes
Using precompiled headers .............. no
[...]
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-16 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 10:39 [Buildroot] [Bug 12906] New: qt PrefixPath is wrong on 2020.05-rc1 bugzilla at busybox.net
2020-05-16 12:07 ` [Buildroot] [Bug 12906] " bugzilla at busybox.net
2020-05-16 15:50 ` bugzilla at busybox.net
2020-05-16 16:12 ` bugzilla at busybox.net
2020-05-16 16:38 ` bugzilla at busybox.net [this message]
2020-05-16 20:41 ` bugzilla at busybox.net
2020-05-17 7:25 ` bugzilla at busybox.net
2020-05-17 7:41 ` bugzilla at busybox.net
2020-05-17 10:36 ` bugzilla at busybox.net
2020-05-17 19:27 ` bugzilla at busybox.net
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-12906-163-DfksbfyoAh@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