Same message on a lot of packages: -- Detecting CXX compile features - done -- CMake Error at /usr/lib64/cmake/Qt5Core/Qt5CoreConfig.cmake:27 (message): The imported target "Qt5::Core" references the file "/usr/lib64/qt5/bin/qdoc" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib64/cmake/Qt5Core/Qt5CoreConfigExtras.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib64/cmake/Qt5Core/Qt5CoreConfigExtras.cmake:41 (_qt5_Core_check_file_exists) /usr/lib64/cmake/Qt5Core/Qt5CoreConfig.cmake:158 (include) /usr/lib64/cmake/Qt5DBus/Qt5DBusConfig.cmake:99 (find_package) /usr/lib64/cmake/Qt5/Qt5Config.cmake:26 (find_package) CMakeLists.txt:13 (find_package) -- Configuring incomplete, errors occurred!
Could you please grep for "qdoc" /usr/lib64/cmake/Qt5* and attach a sample file?
Created attachment 436914 [details] build.log grep qdoc /usr/lib64/cmake/Qt5* grep: /usr/lib64/cmake/Qt5: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Concurrent: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Core: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5DBus: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Designer: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Gui: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5LinguistTools: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Multimedia: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5MultimediaWidgets: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Network: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5OpenGL: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5OpenGLExtensions: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5PrintSupport: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Qml: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Quick: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5QuickTest: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5QuickWidgets: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Script: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5ScriptTools: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Sql: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Svg: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Test: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5UiPlugin: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5UiTools: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Widgets: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5X11Extras: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5Xml: Ist ein Verzeichnis grep: /usr/lib64/cmake/Qt5XmlPatterns: Ist ein Verzeichnis grep -ir qdoc /usr/lib64/cmake/Qt5* /usr/lib64/cmake/Qt5Core/Qt5CoreConfigExtras.cmake:if (NOT TARGET Qt5::qdoc) /usr/lib64/cmake/Qt5Core/Qt5CoreConfigExtras.cmake: add_executable(Qt5::qdoc IMPORTED) /usr/lib64/cmake/Qt5Core/Qt5CoreConfigExtras.cmake: set(imported_location "${_qt5Core_install_prefix}/lib64/qt5/bin/qdoc") /usr/lib64/cmake/Qt5Core/Qt5CoreConfigExtras.cmake: set_target_properties(Qt5::qdoc PROPERTIES Failed packages: ls -l /var/tmp/portage/kde-* /var/tmp/portage/kde-apps: insgesamt 12 drwxr-xr-x 7 portage portage 4096 8. Jun 17:37 gpgmepp-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:42 libkdcraw-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:31 libkexiv2-9999 /var/tmp/portage/kde-frameworks: insgesamt 204 drwxr-xr-x 7 portage portage 4096 8. Jun 17:32 attica-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:36 breeze-icons-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:17 frameworkintegration-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:26 karchive-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:13 kauth-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:15 kbookmarks-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:18 kcmutils-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:28 kcodecs-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:25 kcompletion-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:24 kconfig-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:14 kconfigwidgets-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:17 kcoreaddons-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:27 kcrash-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:26 kdbusaddons-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:18 kdeclarative-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:19 kded-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:37 kdesignerplugin-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:33 kdesu-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:35 kdnssd-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:32 kdoctools-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:33 kemoticons-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:00 kfilemetadata-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:27 kglobalaccel-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:28 kguiaddons-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:24 ki18n-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:14 kiconthemes-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:29 kidletime-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:19 kinit-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:17 kio-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:30 kitemmodels-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:26 kitemviews-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:28 kjobwidgets-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:34 kjs-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:36 kjsembed-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:18 knewstuff-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:16 knotifications-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:34 kpackage-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:17 kparts-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:35 kpeople-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:29 kpty-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:33 kservice-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:15 ktextwidgets-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:35 kunitconversion-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:16 kwallet-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:30 kwayland-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:24 kwidgetsaddons-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:25 kwindowsystem-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 18:15 kxmlgui-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:43 solid-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:29 sonnet-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:31 threadweaver-9999 /var/tmp/portage/kde-plasma: insgesamt 8 drwxr-xr-x 7 portage portage 4096 8. Jun 17:31 kdecoration-9999 drwxr-xr-x 7 portage portage 4096 8. Jun 17:37 libkscreen-9999 qt version is 5.7.9999
I see the same message when I try to emerge cmake.
could be related to this: http://code.qt.io/cgit/qt/qtbase.git/commit/?h=5.7&id=dc0ae02ebc8e221f952829230c0301a718a6f10b "CMake: Add imported target for qdoc."
that all with global USE="-doc"
After I emerged dev-qt/qdoc I was able to emerge cmake again. USE="ncurses qt5 system-jsoncpp -doc -emacs -qt4 {-test}"
I'm not familiar with cmake... what does "if (NOT TARGET Qt5::qdoc)" mean? when is it true, when is it false?
(In reply to Davide Pesavento from comment #7) > I'm not familiar with cmake... what does "if (NOT TARGET Qt5::qdoc)" mean? > when is it true, when is it false? It's creating a Qt5::qdoc target if it doesn't already exist. Unless a consumer provided their own target, I can't think of a reason why it would already exist so I think we can assume it will be true and the block will be executed in most circumstances Effectively it looks like Qt5CoreConfigExtras.cmake is guaranteeing that qdoc will be available in a similar fashion to qmake, moc, and rcc.
(In reply to jospezial from comment #4) > could be related to this: > http://code.qt.io/cgit/qt/qtbase.git/commit/?h=5. > 7&id=dc0ae02ebc8e221f952829230c0301a718a6f10b > "CMake: Add imported target for qdoc." Thanks, that helps a lot.
As I feared... so this effectively means that qtcore:5 has a PDEPEND on qdoc:5 (although this would be true only for packages that use cmake to build). This sounds odd to me, considering that qdoc lives in a separate repo and is not a bootstrapped tool. I hope that they didn't fully realize the implications of that change and merged it by mistake. @jospezial, could you report this issue upstream please?
It's since been reverted: https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/Qt5CoreConfigExtras.cmake.in?id=6583720aa4503fce16b44cce7b8d939058abf000
