src/Load/LoadImageFromUrl.cpp: In member function ‘void LoadImageFromUrl::slotFinished()’: src/Load/LoadImageFromUrl.cpp:61:21: error: variable ‘QTextStream str’ has initializer but incomplete type QTextStream str (&message); ^ src/Load/LoadImageFromUrl.cpp: In member function ‘void LoadImageFromUrl::startLoadImage(const QUrl&)’: ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop_libressl-test_20180728-001933 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.8.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv media-gfx/engauge [ebuild N ] media-gfx/engauge-10.6 USE="pdf -doc -examples -jpeg2k"
Created attachment 541756 [details] emerge-info.txt
Created attachment 541758 [details] emerge-history.txt
Created attachment 541760 [details] environment
Created attachment 541762 [details] etc.portage.tbz2
Created attachment 541764 [details] media-gfx:engauge-10.6:20180730-083759.log
Created attachment 541766 [details] temp.tbz2
Sorry, I can't reproduce. Also, it very much looks like this is an upstream bug. Can you please file a bug upstream?
(In reply to Denis Dupeyron from comment #7) it can be reproduced here at the tinderox - and its marked a s ablocker for QT 5.11
This is a typical bug caused by Qt 5.11, description is in the tracker, just needs a missing header added.
...or not? I was also not able to reproduce this issue on my system.
got at the unstable amd64 chroot image 17.0-developer_libressl_20180816-174630 too
Created attachment 543914 [details] emerge-info.txt
Created attachment 543916 [details] emerge-history.txt
Created attachment 543918 [details] environment
Created attachment 543920 [details] etc.portage.tbz2
Created attachment 543922 [details] media-gfx:engauge-10.6:20180818-080157.log
Created attachment 543924 [details] temp.tbz2
got at the unstable amd64 chroot image 17.0-desktop-gnome-systemd_libressl_20180817-190408 - maybe this 3rd example helps to find the error pattern
Created attachment 543930 [details] emerge-info.txt
Created attachment 543932 [details] emerge-history.txt
Created attachment 543934 [details] environment
Created attachment 543936 [details] etc.portage.tbz2
Created attachment 543938 [details] media-gfx:engauge-10.6:20180818-115308.log
Created attachment 543940 [details] temp.tbz2
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eee92fc66783faa17112955812d026d205310001 commit eee92fc66783faa17112955812d026d205310001 Author: Michael Palimaka <kensington@gentoo.org> AuthorDate: 2018-10-11 13:00:34 +0000 Commit: Michael Palimaka <kensington@gentoo.org> CommitDate: 2018-10-11 13:00:49 +0000 media-gfx/engauge: fix build with Qt 5.11 Closes: https://bugs.gentoo.org/662476 Signed-off-by: Michael Palimaka <kensington@gentoo.org> Package-Manager: Portage-2.3.49, Repoman-2.3.11 media-gfx/engauge/engauge-10.6.ebuild | 4 +++- media-gfx/engauge/files/engauge-10.6-qt-5.11.patch | 26 ++++++++++++++++++++++ 2 files changed, 29 insertions(+), 1 deletion(-)