[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1019226: marked as done (libqt5waylandclient5-dev: Qt5WaylandClientConfig.cmake invalid)

Your message dated Tue, 13 Sep 2022 12:56:15 +0300
with message-id <YyBTvwpwydvvw9ut@mitya57.me>
and subject line Re: Bug#1019226: libqt5waylandclient5-dev: Qt5WaylandClientConfig.cmake invalid
has caused the Debian Bug report #1019226,
regarding libqt5waylandclient5-dev: Qt5WaylandClientConfig.cmake invalid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1019226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019226
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libqt5waylandclient5-dev
Version: 5.15.2-3
Severity: normal
X-Debbugs-Cc: wade@wabyn.net

Dear Maintainer,
This may be user error, but the error message does make it look very much like 
a problem with the package.

Attempting to build 'kwallet' from source using
kdesrc-build kwallet
results in the following error log file:
<<BEGIN_LOG_FILE>>
# kdesrc-build running: 'cmake' '-B' '.' '-S' '/home/wade/kde/src/kwayland'
'-G' 'Unix Makefiles' '-DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=ON'
'-DCMAKE_BUILD_TYPE=RelWithDebInfo' '-DCMAKE_CXX_FLAGS:STRING=-pipe'
'-DCMAKE_INSTALL_PREFIX=/home/wade/kde/usr'
# from directory: /home/wade/Projects/kde/build/kwayland
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
--

Installing in /home/wade/kde/usr. Run
/home/wade/Projects/kde/build/kwayland/prefix.sh to set the environment for
KWayland.
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Performing Test _OFFT_IS_64BIT
-- Performing Test _OFFT_IS_64BIT - Success
-- Performing Test HAVE_DATE_TIME
-- Performing Test HAVE_DATE_TIME - Success
-- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE
-- Performing Test BSYMBOLICFUNCTIONS_AVAILABLE - Success
CMake Error at /usr/lib/x86_64-linux-
gnu/cmake/Qt5WaylandClient/Qt5WaylandClientConfig.cmake:26 (message):
The imported target "Qt5::WaylandClient" references the file

"/usr/include/x86_64-linux-gnu/qt5/QtWaylandClient/5.15.2"

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/lib/x86_64-linux-
gnu/cmake/Qt5WaylandClient/Qt5WaylandClientConfig.cmake"

but not all the files it references.

Call Stack (most recent call first):
/usr/lib/x86_64-linux-
gnu/cmake/Qt5WaylandClient/Qt5WaylandClientConfig.cmake:81
(_qt5_WaylandClient_check_file_exists)
CMakeLists.txt:44 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/wade/Projects/kde/build/kwayland/CMakeFiles/CMakeOutput.log". 
<<END_LOG_FILE>>

Note that the file or directory "/usr/include/x86_64-linux-
gnu/qt5/QtWaylandClient/5.15.2" does not exist in this package; there are no
subdirectories under /usr/include/x86_64-linux-gnu/qt5/QtWaylandClient.

I attempted to install the required dependencies with:
$ apt build-dep -t stable kwalletmanager kwalletcli
$ apt build-dep -t stable libkwaylandserver-dev

It didn't help.

--- Wade

-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,
'stable'), (400, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqt5waylandclient5-dev depends on:
ii libqt5waylandclient5 5.15.2-3

Versions of packages libqt5waylandclient5-dev recommends:
ii qtwayland5-dev-tools 5.15.2-3

libqt5waylandclient5-dev suggests no packages.

--- End Message ---
--- Begin Message --- 
Hi Wade!

On Mon, Sep 05, 2022 at 12:37:42PM -0700, Wade Richards wrote:
> Dear Maintainer,
>
> This may be user error, but the error message does make it look very much
> like a problem with the package.
>
> [...] 
>
> CMake Error at /usr/lib/x86_64-linux-
> gnu/cmake/Qt5WaylandClient/Qt5WaylandClientConfig.cmake:26 (message):
> The imported target "Qt5::WaylandClient" references the file
>
> "/usr/include/x86_64-linux-gnu/qt5/QtWaylandClient/5.15.2"
>
> but this file does not exist.

Private directories are referenced only when the package you are trying to
build needs private headers.

Here is the relevant part of Qt5WaylandClientConfig.cmake:

    # Only check existence of private includes if the Private component is
    # specified.
    list(FIND Qt5WaylandClient_FIND_COMPONENTS Private _check_private)
    if (NOT _check_private STREQUAL -1)
        foreach(_dir ${Qt5WaylandClient_PRIVATE_INCLUDE_DIRS})
            _qt5_WaylandClient_check_file_exists(${_dir})
        endforeach()
    endif()

And KWayland does need them. See "COMPONENTS Private" in this line:
https://invent.kde.org/frameworks/kwayland/-/blob/v5.98.0/CMakeLists.txt#L44

So you should install qtwayland5-private-dev when building KWayland.

(Thanks to everybody who discussed this on IRC today.)

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: