-- Checking for module 'glib-2.0' -- Found glib-2.0, version 2.72.0 -- Checking for module 'gio-unix-2.0' -- Found gio-unix-2.0, version 2.72.0 CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0", minimum required is "2.41.0") ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_systemd-j4-20220319-224115 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): /usr/lib/llvm/13 13.0.1 Python 3.9.11 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.59.0 * php cli: HEAD of ::gentoo commit a62d53ae52b95a65bfc68d0940b802e200bedcde Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sun Mar 20 06:34:32 2022 +0000 2022-03-20 06:34:30 UTC emerge -qpvO dev-libs/libqtxdg [ebuild N ] dev-libs/libqtxdg-3.8.0 USE="-test"
Created attachment 767422 [details] emerge-info.txt
Created attachment 767423 [details] CMakeOutput.log
Created attachment 767424 [details] dev-libs:libqtxdg-3.8.0:20220320-080536.log
Created attachment 767425 [details] emerge-history.txt
Created attachment 767426 [details] environment
Created attachment 767427 [details] etc.portage.tar.bz2
Created attachment 767428 [details] logs.tar.bz2
Created attachment 767429 [details] temp.tar.bz2
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/qt.git/commit/?id=0177ce4bbcca1d8d2a0cf32ecd3fab788209a414 commit 0177ce4bbcca1d8d2a0cf32ecd3fab788209a414 Author: Jimi Huotari <chiitoo@gentoo.org> AuthorDate: 2022-03-20 18:03:55 +0000 Commit: Jimi Huotari <chiitoo@gentoo.org> CommitDate: 2022-03-20 18:04:35 +0000 dev-libs/libqtxdg: add dev-libs/glib dependency Bug: https://bugs.gentoo.org/835648 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Jimi Huotari <chiitoo@gentoo.org> dev-libs/libqtxdg/libqtxdg-9999.ebuild | 1 + 1 file changed, 1 insertion(+)
That's definitely an issue with >=dev-libs/glib-2.72.0 (or even 2.71 development versions according to this RedHat bug: https://bugzilla.redhat.com/show_bug.cgi?id=2045799#c5). Downgrading to dev-libs/glib-2.70.4 "fixes" this issue.
(In reply to Lars Wendler (Polynomial-C) from comment #10) > That's definitely an issue with >=dev-libs/glib-2.72.0 (or even 2.71 > development versions according to this RedHat bug: > https://bugzilla.redhat.com/show_bug.cgi?id=2045799#c5). Downgrading to > dev-libs/glib-2.70.4 "fixes" this issue. Does the patch from https://github.com/lxqt/libfm-qt/issues/776 work?
>>> Emerging (9 of 11) dev-libs/libqtxdg-3.8.0::gentoo * libqtxdg-3.8.0.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking libqtxdg-3.8.0.tar.xz to /var/tmp/portage/dev-libs/libqtxdg-3.8.0/work >>> Source unpacked in /var/tmp/portage/dev-libs/libqtxdg-3.8.0/work >>> Preparing source in /var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0 ... * Source directory (CMAKE_USE_DIR): "/var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0" * Build directory (BUILD_DIR): "/var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0_build" >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0 ... * Source directory (CMAKE_USE_DIR): "/var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0" * Build directory (BUILD_DIR): "/var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0_build" cmake -C /var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0_build/gentoo_common_config.cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/usr -DBUILD_TESTS=no -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_TOOLCHAIN_FILE=/var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0_build/gentoo_toolchain.cmake /var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0 loading initial cache file /var/tmp/portage/dev-libs/libqtxdg-3.8.0/work/libqtxdg-3.8.0_build/gentoo_common_config.cmake -- The C compiler identification is GNU 11.2.1 -- The CXX compiler identification is GNU 11.2.1 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc - 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/x86_64-pc-linux-gnu-g++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found PkgConfig: /usr/bin/x86_64-pc-linux-gnu-pkg-config (found version "1.8.0") -- Checking for module 'glib-2.0' -- Found glib-2.0, version 2.72.0 -- Checking for module 'gio-unix-2.0' -- Found gio-unix-2.0, version 2.72.0 CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find GLIB (missing: GLIB_GIO_UNIX_INCLUDE_DIR) (found suitable version "2.72.0", minimum required is "2.41.0") Call Stack (most recent call first): /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake/lxqt-build-tools/find-modules/FindGLIB.cmake:113 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) CMakeLists.txt:26 (find_package)
(In reply to HougeLangley from comment #12) Don't need another log -- need someone to test the patch I linked. Thanks!
(In reply to Sam James from comment #13) > (In reply to HougeLangley from comment #12) > > Don't need another log -- need someone to test the patch I linked. Thanks! Oh, my apologize
*** Bug 836015 has been marked as a duplicate of this bug. ***
*** Bug 835691 has been marked as a duplicate of this bug. ***
Heh, I did read the error message a bit too quick-like it seems, as if the dependency was missing (which it was). This should be fixed in git master of 'lxqt-build-tools' [1]. 1. https://github.com/lxqt/lxqt-build-tools/commit/62b77bb807aa2ac2c1df8eec372df771da8d2203
(In reply to Chiitoo from comment #17) > This should be fixed in git master of 'lxqt-build-tools' [1]. > > 1. > https://github.com/lxqt/lxqt-build-tools/commit/ > 62b77bb807aa2ac2c1df8eec372df771da8d2203 I can confirm the fix to be working for the live ebuilds of libqtxdg and libfm-qt, after updating lxqt-build-tools-9999.
(In reply to Bernd from comment #18) > (In reply to Chiitoo from comment #17) > > This should be fixed in git master of 'lxqt-build-tools' [1]. > > > > 1. > > https://github.com/lxqt/lxqt-build-tools/commit/ > > 62b77bb807aa2ac2c1df8eec372df771da8d2203 > > I can confirm the fix to be working for the live ebuilds of libqtxdg and > libfm-qt, after updating lxqt-build-tools-9999. Yes, I have been tested, problem solved.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f21c0b5fc563408466284a7fcb06a1a5ce0974f commit 1f21c0b5fc563408466284a7fcb06a1a5ce0974f Author: Jimi Huotari <chiitoo@gentoo.org> AuthorDate: 2022-03-31 13:49:48 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-04-04 21:43:55 +0000 dev-util/lxqt-build-tools: fix build-issues with glib-2.72 This patches in a fix for CMake-time issues with 'dev-libs/libqtxdg' and 'x11-libs/libfm-qt'. Closes: https://bugs.gentoo.org/835648 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Jimi Huotari <chiitoo@gentoo.org> Closes: https://github.com/gentoo/gentoo/pull/24835 Signed-off-by: Sam James <sam@gentoo.org> .../files/lxqt-build-tools-0.10.0-glib-2.72.patch | 25 +++++++++++++++++++ .../lxqt-build-tools-0.10.0-r1.ebuild | 28 ++++++++++++++++++++++ 2 files changed, 53 insertions(+)
This still happens with x11-libs/libfm-qt-1.1.0 (stable) and 1.2.0 (~amd64).
It seems to be solved in version 0.12.0 - unmasking it allowed the update to complete.
Can confirm that installing lxqt-build-tools-0.12.0 fixes the issue with libfm-qt-1.1.0.
I was also having build failures with dev-libs/libqtxdg-3.9.1 and x11-libs/libfm-qt-1.1.0, and upgrading to dev-util/lxqt-build-tools-0.12.0 fixed it.
Filed stable bug as bug 884385.
If I recall right-like, an issue pretty much identical to the old patch creeped up later on, and as such the patch did not carry over from 0.10.0 to 0.11.0. I meant to see to it that it gets fixed in time, but then forgot/did not have time, and now that people started getting hit with it, I /really/ did not have time. Thank you Sam (and Mike) for the stable bug(s) and apologies for the trouble!
