[kdepim] [Bug 410474] kde-apps/kdepim-runtime-19.04.3 with parallel build gives fatal error: ui_lockfilepage.h: No such file or directory

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sat Sep 21 11:05:09 BST 2019


https://bugs.kde.org/show_bug.cgi?id=410474

--- Comment #8 from andreas.sturmlechner at gmail.com ---
(In reply to Christophe Giboudeaux from comment #6)
> what is gentoo_common_config.cmake ?
This enforces global cmake projects packaging settings (copy from my own
system):

> SET (CMAKE_GENTOO_BUILD ON CACHE BOOL "Indicate Gentoo package build")
> SET (LIB_SUFFIX 64 CACHE STRING "library path suffix" FORCE)
> SET (CMAKE_INSTALL_LIBDIR lib64 CACHE PATH "Output directory for libraries")
> SET (CMAKE_INSTALL_INFODIR "/usr/share/info" CACHE PATH "")
> SET (CMAKE_INSTALL_MANDIR "/usr/share/man" CACHE PATH "")
> SET (CMAKE_USER_MAKE_RULES_OVERRIDE "/var/tmp/portage/kde-apps/kdepim-runtime-19.08.1/work/kdepim-runtime-19.08.1_build/gentoo_rules.cmake" CACHE FILEPATH "Gentoo override rules")
> SET (CMAKE_INSTALL_DOCDIR "/usr/share/doc/kdepim-runtime-19.08.1" CACHE PATH "")
> SET (BUILD_SHARED_LIBS ON CACHE BOOLEAN "")

(In reply to Christophe Giboudeaux from comment #6)
> same for gentoo_toolchain.cmake
Also from packaging for cmake projects (copy from my own system):

> SET (CMAKE_ASM_COMPILER "x86_64-pc-linux-gnu-gcc")
> SET (CMAKE_ASM-ATT_COMPILER "x86_64-pc-linux-gnu-gcc")
> SET (CMAKE_C_COMPILER "x86_64-pc-linux-gnu-gcc")
> SET (CMAKE_CXX_COMPILER "x86_64-pc-linux-gnu-g++")
> SET (CMAKE_Fortran_COMPILER "x86_64-pc-linux-gnu-gfortran")
> SET (CMAKE_AR /usr/bin/x86_64-pc-linux-gnu-ar CACHE FILEPATH "Archive manager" FORCE)
> SET (CMAKE_RANLIB /usr/bin/x86_64-pc-linux-gnu-ranlib CACHE FILEPATH "Archive index generator" FORCE)
> SET (CMAKE_SYSTEM_PROCESSOR "x86_64")

(In reply to Christophe Giboudeaux from comment #6)
> What does -DCMAKE_BUILD_TYPE=Gentoo do exactly?
It is to enforce global compiler flags on all packages. There is a summary of
the Gentoo configuration in build.log at the end of configure by example of the
downstream report, nothing strikes me as out of the ordinary there, it is
reflective of the user's CFLAGS/CXXFLAGS settings shown in the first
(downstream) comment.

copied from downstream user's build.log:
> -- <<< Gentoo configuration >>>
> Build type      Gentoo
> Install path    /usr
> Compiler flags:
> C               -O2 -march=native -pipe -fomit-frame-pointer -std=iso9899:1990 -fno-common -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings -Werror=implicit-function-declaration
> C++             -O2 -march=native -pipe -fomit-frame-pointer -std=c++0x -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -fdiagnostics-color=always -pedantic -Wzero-as-null-pointer-constant
> Linker flags:
> Executable      -Wl,--enable-new-dtags -Wl,-O1 -Wl,--as-needed
> Module          -Wl,--no-undefined -Wl,--enable-new-dtags -Wl,-O1 -Wl,--as-needed
> Shared          -Wl,--no-undefined -Wl,--enable-new-dtags -Wl,-O1 -Wl,--as-needed

(In reply to Christophe Giboudeaux from comment #6)
> is it reproducible if optional dependencies are not disabled (ie: no
> -DCMAKE_DISABLE_FIND_PACKAGE_Libkolabxml=ON)
This is the only optional dependency here and in Gentoo indeed non-optional;
libkolabxml package was removed from the official repo years ago.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Kdepim-bugs mailing list