I tried to install kdenlive-0.9.2. It requires mlt with USE flag qt4. But i tries to compile with qt5 which is also on this machine, and it fails because some tweaks would be needed. Error is "QApplication: No such file or directory", for which I found an explanation at https://qt-project.org/forums/viewthread/23425 Reproducible: Always
Created attachment 386944 [details] Build log
Created attachment 386946 [details] emerge--info
Created attachment 386948 [details] Output-emerge-qv
> Qt version 3.x detected, will compile Qt3 qimage producer > Include directory: /usr/qt/3/include It looks to not be detecting your Qt 4, rather than mis-detecting Qt 5. Which version of Qt 4 do you have installed, and are you using qtchooser at all? Is QTDIR envvar exported in your environment at all?
Misdetecting Qt5? I guess that directory called '/usr/qt/3/include' really contains Qt3, but build is broken because in qt3 you were supposed to include qapplication.h header and not QtGui/QApplication I suppose that the problem is that upstream developers forgot to remove qt3 support when they started to use qt4-only features. This bug should no longer block qt5 tracker bug as it seems to be a problem with qt3 support. [1] http://www.qtforum.org/article/37604/qapplication-no-such-file-or-directory.html [2] http://doc.qt.digia.com/3.3/qapplication.html
(In reply to Paweł Stankowski from comment #5) > Misdetecting Qt5? I guess that directory called '/usr/qt/3/include' really > contains Qt3, but build is broken because in qt3 you were supposed to > include qapplication.h header and not QtGui/QApplication > > I suppose that the problem is that upstream developers forgot to remove qt3 > support when they started to use qt4-only features. This bug should no > longer block qt5 tracker bug as it seems to be a problem with qt3 support. > > [1] > http://www.qtforum.org/article/37604/qapplication-no-such-file-or-directory. > html > [2] http://doc.qt.digia.com/3.3/qapplication.html This build system assumes that if Qt 4 cannot be detected for whatever reason, that Qt 3 is definitely present. Given that Qt 3 has been removed from portage for over 4 years, it seems more likely that there is some issue with Qt 4 being detected (which may or may not be related to Qt 5) rather than some random Qt 3 build failure.
Thank very much to all for the support. I have the following comments: * I do not have qtchooser installed (it is blocked by stable version qtcore-4.8.5). It does ot seem to be compulsory to all packacges, for example owncloud-client can be compiled with qt4 or qt5 without qtchooser (see bug #512726). * I did have qt-meta:3 from kde-sunset overlay installed (before May 2013, qucs was only in kde-sunset with qt3; then it was imported into main tree with qt4 support, and by that time I had forgotten to uninstall qt3). After uninstalling qt-meta:3, mlt compiled fine.
Huh, that's a surprise to see Qt 3 still in use. :-)
*** Bug 536510 has been marked as a duplicate of this bug. ***
Confirmed: I have the same error and dev-qt/qt-meta-3.3.8b-r2 emerged from overlay kde-sunset. Trying to unmerge it now.
0.9.8 appears to drop support for Qt 3 so this should no longer be an issue.
