Re: [Interest] 5.11.3 make install failure
On Monday, 14 January 2019 11:46:10 PST Giuseppe D'Angelo via Interest wrote: > It's *way* more likely that there's a bug in the dependency ordering of > some modules; a highly parallel build would hit the bug by trying to > compile a module before its prerequisite. (This also means why running > make multiple times doesn't help, and actually might make the bug "go > away" by compiling the prerequisite.) True, although I did a make -j160 close to the 5.12.0 release and did not see this problem. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
On Monday, 14 January 2019 11:57:46 PST Jason H wrote:
> qWarning() does not require , it is provided via . Only
> qDebug() stream operator syntax requires the #include
> http://doc.qt.io/qt-5/debug.html
> "If you include the header file, the qDebug() macro can also be
> used as an output stream."
To be clear:
qDebug("foo");
only requires , but
qDebug() << "foo";
requires
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
Quoting Jason H : I gave up. Nothing beyond 5.9.7 appears to compile correctly. It's not a GCC issue either. The same -j option and same configure command work just fine for 5.9.7 and everything else just trashes. I have to get something functional so no further effort on 5.11.x. I know that's not true because I've compiled 5.11.2 myself. Albeit, with the make issues, but it eventually built. Truth is based on the environment. In this environment "eventually built" != "built first pass" so it is not allowed to be used. One cannot file a regulatory document for independent QA saying "Just keep ignoring build failures and resubmitting until it actually completes." In environments without controls or regulations "eventually built" is probably just fine, providing someone bothers to keep trying. -- Roland Hughes, President Logikal Solutions (630) 205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog http://lesedi.us ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
Il 14/01/19 21:52, Jason H ha scritto: I would have thought that make would have topologically sorted that out by now. ¯\_(ツ)_/¯ I mean, the makefile itself*is* the dependency graph. Any list of files with no dependencies should be a pool that can be compiled in any order. I've always structure my source tree and made my makefiles this way, so they "just work". To do otherwise is to improperly wield the tool. What would be needed to fix the issue? Is it the configure script failing, or some other part of the makefile generation? Neither; just dependencies across submodules or subdirs in the same module not being written in the .pro files. Thus qmake doesn't generate dependency information, thus make will not build (if you're unlucky). My 2 c, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts smime.p7s Description: Firma crittografica S/MIME ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
> Il 14/01/19 18:46, Jason H ha scritto: > > It took repeated `make`s to finally build. Never failed repeatedly in the > > same place. I think this is a GCC issue, or some combination of linux+gcc. > > Decreasing the J made it happen less, but maybe that's just because it's > > compiling less? Without a reliable failure case I could not identify it > > further. > > It's *way* more likely that there's a bug in the dependency ordering of > some modules; a highly parallel build would hit the bug by trying to > compile a module before its prerequisite. (This also means why running > make multiple times doesn't help, and actually might make the bug "go > away" by compiling the prerequisite.) I would have thought that make would have topologically sorted that out by now. ¯\_(ツ)_/¯ I mean, the makefile itself *is* the dependency graph. Any list of files with no dependencies should be a pool that can be compiled in any order. I've always structure my source tree and made my makefiles this way, so they "just work". To do otherwise is to improperly wield the tool. What would be needed to fix the issue? Is it the configure script failing, or some other part of the makefile generation? ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
> I gave up. Nothing beyond 5.9.7 appears to compile correctly. It's not > a GCC issue either. The same -j option and same configure command work > just fine for 5.9.7 and everything else just trashes. I have to get > something functional so no further effort on 5.11.x. I know that's not true because I've compiled 5.11.2 myself. Albeit, with the make issues, but it eventually built. > I don't know how 5.12.0 could have passed compilation with any > configure command though. It calls qWarning() and does not have qdebug > header file. qWarning() does not require , it is provided via . Only qDebug() stream operator syntax requires the #include http://doc.qt.io/qt-5/debug.html "If you include the header file, the qDebug() macro can also be used as an output stream." ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
Il 14/01/19 18:46, Jason H ha scritto: It took repeated `make`s to finally build. Never failed repeatedly in the same place. I think this is a GCC issue, or some combination of linux+gcc. Decreasing the J made it happen less, but maybe that's just because it's compiling less? Without a reliable failure case I could not identify it further. It's *way* more likely that there's a bug in the dependency ordering of some modules; a highly parallel build would hit the bug by trying to compile a module before its prerequisite. (This also means why running make multiple times doesn't help, and actually might make the bug "go away" by compiling the prerequisite.) My 2 c, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts smime.p7s Description: Firma crittografica S/MIME ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
Den mån 14 jan. 2019 kl 18:53 skrev :
>
>
> Quoting Elvis Stansvik :
>
> > Den mån 14 jan. 2019 17:38Jason H skrev:
> >
> >> Applying Occam's razor,
> >> I think your make is failing, make install is making the default target
> >> (resuming your broken build, and failing again) and not actually getting to
> >> install?
> >>
> >> Can you confirm your make of the default target ended successfully?
> >>
> >
> > Note also that using make -jN, the error may in some cases not be
> > immediately obvious from the last bit of output, but is visible some pages
> > up. Search backwards for errors or do a serial build to be sure.
> >
> > Elvis
> >
>
> Was using 5.12.0 with following configure command
>
> ./configure -prefix /home/developer/Qt-5.12.0 -no-xcb -opensource
> -confirm-license -system-freetype -system-pcre -no-harfbuzz -no-xcb
> -nomake examples -no-sql-mysql -shared -no-sql-psql -no-sqlite
> -enable-linuxfb -no-directfb -widgets --enable-linuxfb -no-directfb
> -no-xcb -no-opengl -no-eglfs -no-openssl -fontconfig -no-gif
> -no-libjpeg -system-libpng -no-dbus -no-tslib -no-glib -icu -libinput
> -no-gtk
>
> Wow, it was over 500 lines back. Still doesn't explain how that source
> file could have this code
>
> void QWaylandIviSurface::sendConfigure(const QSize &size)
> {
> if (!size.isValid()) {
> qWarning() << "Can't configure ivi_surface with an invalid
> size" << size;
> return;
> }
> Q_D(QWaylandIviSurface);
> d->send_configure(size.width(), size.height());
> }
>
> and not include qdebug header file.
My only guess is that it perhaps (sloppily) relies on it being
transitively included, but that something along the way to that
#include is conditional and happen to be excluded with your
particular combination of configure flags (which may be untested).
Just a long shot..
Elvis
>
> g++ -c -include .pch/Qt5XmlPatterns -pipe -O2 -std=c++1z
> -fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -Wvla
> -Wdate-time -Wshift-overflow=2 -Wduplicated-cond
> -Wno-stringop-overflow -D_REENTRANT -fPIC -DQT_NO_FOREACH
> -DQT_NO_USING_NAMESPACE
> -DQT_ENABLE_QEXPLICITLYSHAREDDATAPOINTER_STATICCAST
> -DYYLTYPE_IS_DECLARED=1 -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT
> -DQT_BUILD_XMLPATTERNS_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII
> -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER
> -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x05
> -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG
> -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Iacceltree -Idata -Iapi
> -Ienvironment -Iexpr -Ifunctions -Iiterators -Ijanitors -Iparser
> -Ischema -Itype -Iutils -I../../include -I../../include/QtXmlPatterns
> -I../../include/QtXmlPatterns/5.12.0
> -I../../include/QtXmlPatterns/5.12.0/QtXmlPatterns
> -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/5.12.0
>
> -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/5.12.0/QtCore
> -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include
> -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtNetwork
> -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore
> -I.moc
> -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/mkspecs/linux-g++
> -o .obj/qrangevariablereference.o
> expr/qrangevariablereference.cpp
> extensions/qwaylandivisurface.cpp: In member function ‘void
> QWaylandIviSurface::sendConfigure(const QSize&)’:
> extensions/qwaylandivisurface.cpp:202:18: error: invalid use of
> incomplete type ‘class QDebug’
> qWarning() << "Can't configure ivi_surface with an invalid
> size" << size;
>^
> In file included from
> /home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/qlogging.h:1:0,
> from
> /home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/../../src/corelib/global/qglobal.h:1200,
> from
> /home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/qglobal.h:1,
> from
> /home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtGui/../../src/gui/kernel/qtguiglobal.h:43,
> from
> /home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtGui/qtguiglobal.h:1,
> from
> ../../include/QtWaylandCompositor/../../src/compositor/global/qtwaylandcompositorglobal.h:54,
> from
> ../../include/QtWaylandCompositor/qtwaylandcompositorglobal.h:1,
> from
> ../../include/QtWaylandCompositor/../../src/compositor/global/qwaylandcompositorextension.h:43,
> from
> ../../include/QtWaylandCompositor/qwaylandcompositorextension.h:1,
> from
> ../../include/QtWaylandCompositor/QWaylandCompositorExtension:1,
> from
> ../../include/QtWaylandCompositor/../../src/compositor/extensions/qwaylandshellsurface.h:43,
> from
> ../../include/QtWaylandC
Re: [Interest] 5.11.3 make install failure
Quoting Jason H : Sent: Monday, January 14, 2019 at 12:56 PM From: rol...@logikalsolutions.com To: "Jason H" Cc: "Elvis Stansvik" , "interest@qt-project.org Interest" Subject: Re: [Interest] 5.11.3 make install failure Quoting Jason H : > Yes, I've seen that too, even on my 8 core/16 thread build server > which 64GB, _never_ touches swap. > It took repeated `make`s to finally build. Never failed repeatedly > in the same place. I think this is a GCC issue, or some combination > of linux+gcc. Decreasing the J made it happen less, but maybe that's > just because it's compiling less? Without a reliable failure case I > could not identify it further. > > Before you leave the client for the day, I'd probably put `make` in > a loop until the exit code is 0, then issue a `make install` > Well, 5.12.0 repeatedly fails in the exact same spot. I can't waste more time on this. 5.9.7 successfully builds first pass every time no matter the -j option. Everything after that seems to wig out and die no matter what configure command I use. I agree with you, that it should only take one invocation. In my experience, it's not Qt, it's the code. Though if what Thiago suggested, make -kjN || make -j1 is what they are using on the COIN servers, it might be why they have not seen it yet. Meanwhile, report that spot (if you haven't already). I've not tried compiling 5.12 yet, just 5.11.3. What about your experience with 5.11.3? I gave up. Nothing beyond 5.9.7 appears to compile correctly. It's not a GCC issue either. The same -j option and same configure command work just fine for 5.9.7 and everything else just trashes. I have to get something functional so no further effort on 5.11.x. I don't know how 5.12.0 could have passed compilation with any configure command though. It calls qWarning() and does not have qdebug header file. -- Roland Hughes, President Logikal Solutions (630) 205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog http://lesedi.us ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
On Monday, 14 January 2019 09:53:15 PST rol...@logikalsolutions.com wrote:
> Wow, it was over 500 lines back. Still doesn't explain how that source
> file could have this code
>
> void QWaylandIviSurface::sendConfigure(const QSize &size)
> {
> if (!size.isValid()) {
> qWarning() << "Can't configure ivi_surface with an invalid
> size" << size;
> return;
> }
> Q_D(QWaylandIviSurface);
> d->send_configure(size.width(), size.height());
> }
>
> and not include qdebug header file.
Because, as I explained twice, the developer used precompiled headers, which
inject a full include to everything outside of QtCore.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
> Sent: Monday, January 14, 2019 at 12:56 PM > From: rol...@logikalsolutions.com > To: "Jason H" > Cc: "Elvis Stansvik" , "interest@qt-project.org Interest" > > Subject: Re: [Interest] 5.11.3 make install failure > > > Quoting Jason H : > > > Yes, I've seen that too, even on my 8 core/16 thread build server > > which 64GB, _never_ touches swap. > > It took repeated `make`s to finally build. Never failed repeatedly > > in the same place. I think this is a GCC issue, or some combination > > of linux+gcc. Decreasing the J made it happen less, but maybe that's > > just because it's compiling less? Without a reliable failure case I > > could not identify it further. > > > > Before you leave the client for the day, I'd probably put `make` in > > a loop until the exit code is 0, then issue a `make install` > > > > Well, 5.12.0 repeatedly fails in the exact same spot. > > I can't waste more time on this. 5.9.7 successfully builds first pass > every time no matter the -j option. Everything after that seems to wig > out and die no matter what configure command I use. I agree with you, that it should only take one invocation. In my experience, it's not Qt, it's the code. Though if what Thiago suggested, make -kjN || make -j1 is what they are using on the COIN servers, it might be why they have not seen it yet. Meanwhile, report that spot (if you haven't already). I've not tried compiling 5.12 yet, just 5.11.3. What about your experience with 5.11.3? ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
Quoting Jason H : Yes, I've seen that too, even on my 8 core/16 thread build server which 64GB, _never_ touches swap. It took repeated `make`s to finally build. Never failed repeatedly in the same place. I think this is a GCC issue, or some combination of linux+gcc. Decreasing the J made it happen less, but maybe that's just because it's compiling less? Without a reliable failure case I could not identify it further. Before you leave the client for the day, I'd probably put `make` in a loop until the exit code is 0, then issue a `make install` Well, 5.12.0 repeatedly fails in the exact same spot. I can't waste more time on this. 5.9.7 successfully builds first pass every time no matter the -j option. Everything after that seems to wig out and die no matter what configure command I use. -- Roland Hughes, President Logikal Solutions (630) 205-1593 http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.johnsmith-book.com http://www.logikalblog.com http://www.interestingauthors.com/blog http://lesedi.us ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
Quoting Elvis Stansvik :
Den mån 14 jan. 2019 17:38Jason H skrev:
Applying Occam's razor,
I think your make is failing, make install is making the default target
(resuming your broken build, and failing again) and not actually getting to
install?
Can you confirm your make of the default target ended successfully?
Note also that using make -jN, the error may in some cases not be
immediately obvious from the last bit of output, but is visible some pages
up. Search backwards for errors or do a serial build to be sure.
Elvis
Was using 5.12.0 with following configure command
./configure -prefix /home/developer/Qt-5.12.0 -no-xcb -opensource
-confirm-license -system-freetype -system-pcre -no-harfbuzz -no-xcb
-nomake examples -no-sql-mysql -shared -no-sql-psql -no-sqlite
-enable-linuxfb -no-directfb -widgets --enable-linuxfb -no-directfb
-no-xcb -no-opengl -no-eglfs -no-openssl -fontconfig -no-gif
-no-libjpeg -system-libpng -no-dbus -no-tslib -no-glib -icu -libinput
-no-gtk
Wow, it was over 500 lines back. Still doesn't explain how that source
file could have this code
void QWaylandIviSurface::sendConfigure(const QSize &size)
{
if (!size.isValid()) {
qWarning() << "Can't configure ivi_surface with an invalid
size" << size;
return;
}
Q_D(QWaylandIviSurface);
d->send_configure(size.width(), size.height());
}
and not include qdebug header file.
g++ -c -include .pch/Qt5XmlPatterns -pipe -O2 -std=c++1z
-fvisibility=hidden -fvisibility-inlines-hidden -Wall -W -Wvla
-Wdate-time -Wshift-overflow=2 -Wduplicated-cond
-Wno-stringop-overflow -D_REENTRANT -fPIC -DQT_NO_FOREACH
-DQT_NO_USING_NAMESPACE
-DQT_ENABLE_QEXPLICITLYSHAREDDATAPOINTER_STATICCAST
-DYYLTYPE_IS_DECLARED=1 -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT
-DQT_BUILD_XMLPATTERNS_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII
-DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER
-DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x05
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG
-DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Iacceltree -Idata -Iapi
-Ienvironment -Iexpr -Ifunctions -Iiterators -Ijanitors -Iparser
-Ischema -Itype -Iutils -I../../include -I../../include/QtXmlPatterns
-I../../include/QtXmlPatterns/5.12.0
-I../../include/QtXmlPatterns/5.12.0/QtXmlPatterns
-I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/5.12.0 -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/5.12.0/QtCore -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtNetwork -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore -I.moc -I/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/mkspecs/linux-g++ -o .obj/qrangevariablereference.o
expr/qrangevariablereference.cpp
extensions/qwaylandivisurface.cpp: In member function ‘void
QWaylandIviSurface::sendConfigure(const QSize&)’:
extensions/qwaylandivisurface.cpp:202:18: error: invalid use of
incomplete type ‘class QDebug’
qWarning() << "Can't configure ivi_surface with an invalid
size" << size;
^
In file included from
/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/qlogging.h:1:0,
from
/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/../../src/corelib/global/qglobal.h:1200,
from
/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/qglobal.h:1,
from
/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtGui/../../src/gui/kernel/qtguiglobal.h:43,
from
/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtGui/qtguiglobal.h:1,
from
../../include/QtWaylandCompositor/../../src/compositor/global/qtwaylandcompositorglobal.h:54,
from
../../include/QtWaylandCompositor/qtwaylandcompositorglobal.h:1,
from
../../include/QtWaylandCompositor/../../src/compositor/global/qwaylandcompositorextension.h:43,
from
../../include/QtWaylandCompositor/qwaylandcompositorextension.h:1,
from
../../include/QtWaylandCompositor/QWaylandCompositorExtension:1,
from
../../include/QtWaylandCompositor/../../src/compositor/extensions/qwaylandshellsurface.h:43,
from
../../include/QtWaylandCompositor/qwaylandshellsurface.h:1,
from
../../include/QtWaylandCompositor/QWaylandShellSurface:1,
from extensions/qwaylandivisurface.h:43,
from extensions/qwaylandivisurface.cpp:40:
/home/developer/qt_5_12_0/qt-everywhere-src-5.12.0/qtbase/include/QtCore/../../src/corelib/global/qlogging.h:57:7: note: forward declaration of ‘class
QDebug’
class QDebug;
^~
Makefile:16704: recipe for target '.obj/qwaylandivisurface.o' fa
Re: [Interest] 5.11.3 make install failure
Yes, I've seen that too, even on my 8 core/16 thread build server which 64GB, _never_ touches swap. It took repeated `make`s to finally build. Never failed repeatedly in the same place. I think this is a GCC issue, or some combination of linux+gcc. Decreasing the J made it happen less, but maybe that's just because it's compiling less? Without a reliable failure case I could not identify it further. Before you leave the client for the day, I'd probably put `make` in a loop until the exit code is 0, then issue a `make install` > Sent: Monday, January 14, 2019 at 12:23 PM > From: rol...@logikalsolutions.com > To: "Elvis Stansvik" > Cc: "Jason H" , "interest@qt-project.org Interest" > > Subject: Re: [Interest] 5.11.3 make install failure > > > There were no errors for many screens back. Make appeared to complete > just fine. "make install" compiled __A LOT__ of stuff before it died > on the last bit. Screen after screen of compiler warnings scrolled past. > > make install shouldn't compile a single module. If it does that is an > EPIC fail. > > I do believe I even ran the make without -j a time or two and got the > same results. Just for grins will try to remember to kick one off > before leaving client site today, let it run while I'm not around to > verify that make worked fine but make install failed. > > Ran into this at last client site as well. Configure command which > worked for many different versions on the same virtual machine around > some release of 5.11 would make clean then gag on make install with a > compilation error. Did not have enough resources to be using -j then. > All was well with 5.9.7. > > Roland > > Quoting Elvis Stansvik : > > > Den mån 14 jan. 2019 17:38Jason H skrev: > > > >> Applying Occam's razor, > >> I think your make is failing, make install is making the default target > >> (resuming your broken build, and failing again) and not actually getting to > >> install? > >> > >> Can you confirm your make of the default target ended successfully? > >> > > > > Note also that using make -jN, the error may in some cases not be > > immediately obvious from the last bit of output, but is visible some pages > > up. Search backwards for errors or do a serial build to be sure. > > > > Elvis > > > > > >> > >> > >> > Sent: Monday, January 14, 2019 at 9:30 AM > >> > From: rol...@logikalsolutions.com > >> > To: interest@qt-project.org > >> > Subject: [Interest] 5.11.3 make install failure > >> > > >> > > >> > I kick off the 5.11.3 build from source using same environment as the > >> > previous 5.12.0 failure. Once again, make install, which shouldn't > >> > compile __anything__ fails with a compilation error after make -j3 ran > >> > just fine. > >> > > >> > What is the point of having configure if make install completely ignores > >> it? > >> > > >> > g++ -c -pipe -O2 -std=c++1z -fvisibility=hidden > >> > -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time > >> > -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow > >> > -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS > >> > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS > >> > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_PLUGIN > >> > -DQT_SERVICE_SUPPORT_LIB -DQT_WAYLANDCLIENT_LIB -DQT_GUI_LIB > >> > -DQT_CORE_LIB -I. > >> > -I../../../../hardwareintegration/client/shm-emulation-server > >> > -I../../../../../include/QtWaylandClient/5.11.3 > >> > -I../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient > >> > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include > >> > > >> -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport > >> -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3 > >> -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3/QtServiceSupport > >> -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3 > >> -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3/QtGui > >> -I../../../../../include -I../../../../../include/QtWaylandClient > >> -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui > >> -I/home/developer/qt_5_11_3/qt-everywhere-sr
Re: [Interest] 5.11.3 make install failure
On Monday, 14 January 2019 09:23:31 PST rol...@logikalsolutions.com wrote: > There were no errors for many screens back. Make appeared to complete > just fine. "make install" compiled __A LOT__ of stuff before it died > on the last bit. Screen after screen of compiler warnings scrolled past. > > make install shouldn't compile a single module. If it does that is an > EPIC fail. make install needs to confirm that stuff compiled before it tries to install. If something failed, it is completely correct in trying to compile again and failing. You need to give us a complete certainty that it did not fail, at all. "many screens back" is not sufficient, you need to scan all the way to the beginning. "appeared to complete" is not sufficient, you need to be certain it did. Easy way to confirm that it did not fail: echo $? If that's not 0, something failed. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
There were no errors for many screens back. Make appeared to complete just fine. "make install" compiled __A LOT__ of stuff before it died on the last bit. Screen after screen of compiler warnings scrolled past. make install shouldn't compile a single module. If it does that is an EPIC fail. I do believe I even ran the make without -j a time or two and got the same results. Just for grins will try to remember to kick one off before leaving client site today, let it run while I'm not around to verify that make worked fine but make install failed. Ran into this at last client site as well. Configure command which worked for many different versions on the same virtual machine around some release of 5.11 would make clean then gag on make install with a compilation error. Did not have enough resources to be using -j then. All was well with 5.9.7. Roland Quoting Elvis Stansvik : Den mån 14 jan. 2019 17:38Jason H skrev: Applying Occam's razor, I think your make is failing, make install is making the default target (resuming your broken build, and failing again) and not actually getting to install? Can you confirm your make of the default target ended successfully? Note also that using make -jN, the error may in some cases not be immediately obvious from the last bit of output, but is visible some pages up. Search backwards for errors or do a serial build to be sure. Elvis > Sent: Monday, January 14, 2019 at 9:30 AM > From: rol...@logikalsolutions.com > To: interest@qt-project.org > Subject: [Interest] 5.11.3 make install failure > > > I kick off the 5.11.3 build from source using same environment as the > previous 5.12.0 failure. Once again, make install, which shouldn't > compile __anything__ fails with a compilation error after make -j3 ran > just fine. > > What is the point of having configure if make install completely ignores it? > > g++ -c -pipe -O2 -std=c++1z -fvisibility=hidden > -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time > -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow > -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_PLUGIN > -DQT_SERVICE_SUPPORT_LIB -DQT_WAYLANDCLIENT_LIB -DQT_GUI_LIB > -DQT_CORE_LIB -I. > -I../../../../hardwareintegration/client/shm-emulation-server > -I../../../../../include/QtWaylandClient/5.11.3 > -I../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3 -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3/QtServiceSupport -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3 -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3/QtGui -I../../../../../include -I../../../../../include/QtWaylandClient -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3 -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3/QtCore -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore -I.moc -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/mkspecs/linux-g++ -o .obj/shmserverbufferintegration.o > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp: In function ‘QOpenGLTexture* createTextureFromShm(const QString&, int, int, int, > int)’: > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:81:10: error: ‘QOpenGLContext’ has not been > declared > if (!QOpenGLContext::currentContext()) >^~ > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:59: error: incomplete type ‘QOpenGLTexture’ used in nested name > specifier > auto *tex = new QOpenGLTexture(image, > QOpenGLTexture::DontGenerateMipMaps); > ^~~ > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:78: error: invalid use of incomplete type ‘class > QOpenGLTexture’ > auto *tex = new QOpenGLTexture(image, > QOpenGLTexture::DontGenerateMipMaps); > > ^ > In file included from > ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/qwaylandserverbufferintegration_p.h:1:0, > from > ../../../../hardwareintegration/cli
Re: [Interest] 5.11.3 make install failure
On Monday, 14 January 2019 08:50:42 PST Elvis Stansvik wrote: > Note also that using make -jN, the error may in some cases not be > immediately obvious from the last bit of output, but is visible some pages > up. Search backwards for errors or do a serial build to be sure. To be sure you're building everything when using -j, I recommend running make twice: make -kjN || make -j1 That way, if the first make fails, the second one will stop at the *first* error and not continue. The -k is so that it builds as much as it can, in the assumption that you'll fix the error and continue building. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] 5.11.3 make install failure
Den mån 14 jan. 2019 17:38Jason H skrev: > Applying Occam's razor, > I think your make is failing, make install is making the default target > (resuming your broken build, and failing again) and not actually getting to > install? > > Can you confirm your make of the default target ended successfully? > Note also that using make -jN, the error may in some cases not be immediately obvious from the last bit of output, but is visible some pages up. Search backwards for errors or do a serial build to be sure. Elvis > > > > Sent: Monday, January 14, 2019 at 9:30 AM > > From: rol...@logikalsolutions.com > > To: interest@qt-project.org > > Subject: [Interest] 5.11.3 make install failure > > > > > > I kick off the 5.11.3 build from source using same environment as the > > previous 5.12.0 failure. Once again, make install, which shouldn't > > compile __anything__ fails with a compilation error after make -j3 ran > > just fine. > > > > What is the point of having configure if make install completely ignores > it? > > > > g++ -c -pipe -O2 -std=c++1z -fvisibility=hidden > > -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time > > -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow > > -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS > > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS > > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_PLUGIN > > -DQT_SERVICE_SUPPORT_LIB -DQT_WAYLANDCLIENT_LIB -DQT_GUI_LIB > > -DQT_CORE_LIB -I. > > -I../../../../hardwareintegration/client/shm-emulation-server > > -I../../../../../include/QtWaylandClient/5.11.3 > > -I../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include > > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3 > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3/QtServiceSupport > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3 > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3/QtGui > -I../../../../../include -I../../../../../include/QtWaylandClient > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3 > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3/QtCore > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore > -I.moc > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/mkspecs/linux-g++ > -o .obj/shmserverbufferintegration.o > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp: > In function ‘QOpenGLTexture* createTextureFromShm(const QString&, int, int, > int, > > int)’: > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:81:10: > error: ‘QOpenGLContext’ has not been > > declared > > if (!QOpenGLContext::currentContext()) > >^~ > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:59: > error: incomplete type ‘QOpenGLTexture’ used in nested name > > specifier > > auto *tex = new QOpenGLTexture(image, > > QOpenGLTexture::DontGenerateMipMaps); > > > ^~~ > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:78: > error: invalid use of incomplete type ‘class > > QOpenGLTexture’ > > auto *tex = new QOpenGLTexture(image, > > QOpenGLTexture::DontGenerateMipMaps); > > > > ^ > > In file included from > > > ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/qwaylandserverbufferintegration_p.h:1:0, > > from > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.h:45, > > from > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:40: > > > ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/../../../../../src/client/hardwareintegration/qwaylandserverbufferintegration_p.h:62:7: > note: forward declaration of ‘class > > QOpenGLTexture’ > > class QOpenGLTexture; > > ^~ > > Makefile:12
Re: [Interest] 5.11.3 make install failure
I also realized this (several times in the past) because the make failure happened several hundred lines before but the make process didn't stop. just my 2cent Frank On Monday, 14 January 2019 17:29:58 CET Jason H wrote: > Applying Occam's razor, > I think your make is failing, make install is making the default target > (resuming your broken build, and failing again) and not actually getting to > install? > > Can you confirm your make of the default target ended successfully? > > > Sent: Monday, January 14, 2019 at 9:30 AM > > From: rol...@logikalsolutions.com > > To: interest@qt-project.org > > Subject: [Interest] 5.11.3 make install failure > > > > > > I kick off the 5.11.3 build from source using same environment as the > > previous 5.12.0 failure. Once again, make install, which shouldn't > > compile __anything__ fails with a compilation error after make -j3 ran > > just fine. > > > > What is the point of having configure if make install completely ignores > > it? > > > > g++ -c -pipe -O2 -std=c++1z -fvisibility=hidden > > -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time > > -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow > > -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS > > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS > > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_PLUGIN > > -DQT_SERVICE_SUPPORT_LIB -DQT_WAYLANDCLIENT_LIB -DQT_GUI_LIB > > -DQT_CORE_LIB -I. > > -I../../../../hardwareintegration/client/shm-emulation-server > > -I../../../../../include/QtWaylandClient/5.11.3 > > -I../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServ > > iceSupport > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtSer > > viceSupport/5.11.3 > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtSer > > viceSupport/5.11.3/QtServiceSupport > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui > > /5.11.3 > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui > > /5.11.3/QtGui -I../../../../../include > > -I../../../../../include/QtWaylandClient > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCor > > e/5.11.3 > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCor > > e/5.11.3/QtCore > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCor > > e -I.moc > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/mkspecs/linux > > -g++ -o .obj/shmserverbufferintegration.o > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbuff > > erintegration.cpp > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbuff > > erintegration.cpp: In function ‘QOpenGLTexture* createTextureFromShm(const > > QString&, int, int, int, int)’: > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbuffe > > rintegration.cpp:81:10: error: ‘QOpenGLContext’ has not been declared > > > > if (!QOpenGLContext::currentContext()) > > > >^~ > > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbuffe > > rintegration.cpp:84:59: error: incomplete type ‘QOpenGLTexture’ used in > > nested name specifier > > > > auto *tex = new QOpenGLTexture(image, > > > > QOpenGLTexture::DontGenerateMipMaps); > > > > ^~ > > ~ > > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbuffe > > rintegration.cpp:84:78: error: invalid use of incomplete type ‘class > > QOpenGLTexture’ > > > > auto *tex = new QOpenGLTexture(image, > > > > QOpenGLTexture::DontGenerateMipMaps); > > > > ^ > > > > In file included from > > ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/qway > > landserverbufferintegration_p.h:1:0,> > > from > > > > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbuffe > > rintegration.h:45,> > > from > > > > ../../../../hardwareintegration/client/shm-emul
Re: [Interest] 5.11.3 make install failure
Applying Occam's razor, I think your make is failing, make install is making the default target (resuming your broken build, and failing again) and not actually getting to install? Can you confirm your make of the default target ended successfully? > Sent: Monday, January 14, 2019 at 9:30 AM > From: rol...@logikalsolutions.com > To: interest@qt-project.org > Subject: [Interest] 5.11.3 make install failure > > > I kick off the 5.11.3 build from source using same environment as the > previous 5.12.0 failure. Once again, make install, which shouldn't > compile __anything__ fails with a compilation error after make -j3 ran > just fine. > > What is the point of having configure if make install completely ignores it? > > g++ -c -pipe -O2 -std=c++1z -fvisibility=hidden > -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time > -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow > -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS > -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS > -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_PLUGIN > -DQT_SERVICE_SUPPORT_LIB -DQT_WAYLANDCLIENT_LIB -DQT_GUI_LIB > -DQT_CORE_LIB -I. > -I../../../../hardwareintegration/client/shm-emulation-server > -I../../../../../include/QtWaylandClient/5.11.3 > -I../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3 > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3/QtServiceSupport > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3 > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3/QtGui > -I../../../../../include -I../../../../../include/QtWaylandClient > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3 > > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3/QtCore > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore > -I.moc > -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/mkspecs/linux-g++ > -o .obj/shmserverbufferintegration.o > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp: > In function ‘QOpenGLTexture* createTextureFromShm(const QString&, int, int, > int, > int)’: > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:81:10: > error: ‘QOpenGLContext’ has not been > declared > if (!QOpenGLContext::currentContext()) >^~ > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:59: > error: incomplete type ‘QOpenGLTexture’ used in nested name > specifier > auto *tex = new QOpenGLTexture(image, > QOpenGLTexture::DontGenerateMipMaps); > > ^~~ > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:78: > error: invalid use of incomplete type ‘class > QOpenGLTexture’ > auto *tex = new QOpenGLTexture(image, > QOpenGLTexture::DontGenerateMipMaps); > > ^ > In file included from > ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/qwaylandserverbufferintegration_p.h:1:0, > from > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.h:45, > from > ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:40: > ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/../../../../../src/client/hardwareintegration/qwaylandserverbufferintegration_p.h:62:7: > note: forward declaration of ‘class > QOpenGLTexture’ > class QOpenGLTexture; > ^~ > Makefile:1269: recipe for target '.obj/shmserverbufferintegration.o' failed > make[6]: *** [.obj/shmserverbufferintegration.o] Error 1 > make[6]: Leaving directory > '/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtwayland/src/plugins/hardwareintegration/client/shm-emulation-server' > Makefile:56: recipe for target > 'sub-shm-emulation-server-install_sub
[Interest] 5.11.3 make install failure
I kick off the 5.11.3 build from source using same environment as the previous 5.12.0 failure. Once again, make install, which shouldn't compile __anything__ fails with a compilation error after make -j3 ran just fine. What is the point of having configure if make install completely ignores it? g++ -c -pipe -O2 -std=c++1z -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions -Wall -W -Wvla -Wdate-time -Wshift-overflow=2 -Wduplicated-cond -Wno-stringop-overflow -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_PLUGIN -DQT_SERVICE_SUPPORT_LIB -DQT_WAYLANDCLIENT_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -I../../../../hardwareintegration/client/shm-emulation-server -I../../../../../include/QtWaylandClient/5.11.3 -I../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3 -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtServiceSupport/5.11.3/QtServiceSupport -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3 -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui/5.11.3/QtGui -I../../../../../include -I../../../../../include/QtWaylandClient -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtGui -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3 -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore/5.11.3/QtCore -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/include/QtCore -I.moc -I/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtbase/mkspecs/linux-g++ -o .obj/shmserverbufferintegration.o ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp: In function ‘QOpenGLTexture* createTextureFromShm(const QString&, int, int, int, int)’: ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:81:10: error: ‘QOpenGLContext’ has not been declared if (!QOpenGLContext::currentContext()) ^~ ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:59: error: incomplete type ‘QOpenGLTexture’ used in nested name specifier auto *tex = new QOpenGLTexture(image, QOpenGLTexture::DontGenerateMipMaps); ^~~ ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:84:78: error: invalid use of incomplete type ‘class QOpenGLTexture’ auto *tex = new QOpenGLTexture(image, QOpenGLTexture::DontGenerateMipMaps); ^ In file included from ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/qwaylandserverbufferintegration_p.h:1:0, from ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.h:45, from ../../../../hardwareintegration/client/shm-emulation-server/shmserverbufferintegration.cpp:40: ../../../../../include/QtWaylandClient/5.11.3/QtWaylandClient/private/../../../../../src/client/hardwareintegration/qwaylandserverbufferintegration_p.h:62:7: note: forward declaration of ‘class QOpenGLTexture’ class QOpenGLTexture; ^~ Makefile:1269: recipe for target '.obj/shmserverbufferintegration.o' failed make[6]: *** [.obj/shmserverbufferintegration.o] Error 1 make[6]: Leaving directory '/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtwayland/src/plugins/hardwareintegration/client/shm-emulation-server' Makefile:56: recipe for target 'sub-shm-emulation-server-install_subtargets' failed make[5]: *** [sub-shm-emulation-server-install_subtargets] Error 2 make[5]: Leaving directory '/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtwayland/src/plugins/hardwareintegration/client' Makefile:57: recipe for target 'sub-client-install_subtargets' failed make[4]: *** [sub-client-install_subtargets] Error 2 make[4]: Leaving directory '/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtwayland/src/plugins/hardwareintegration' Makefile:84: recipe for target 'sub-hardwareintegration-install_subtargets' failed make[3]: *** [sub-hardwareintegration-install_subtargets] Error 2 make[3]: Leaving directory '/home/developer/qt_5_11_3/qt-everywhere-src-5.11.3/qtwayland/src/plugins' Makefile:162: recipe for target 'sub-plugins-install_subtargets' failed make[2]: *** [sub-plugins-install_subtargets] Error 2 make[2]: Leaving directory '/home/developer/qt_5_11_
