too long lines were shrinked: | ^~~~~~~~ [160/180] /usr/bin/x86_64-pc-linux-gnu-g++ -DKF_DEPRECATED_WARNINGS_SINCE=0x60000 -DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x56900 -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS_SINCE=0x60000 -DQT_DISABLE_DEPRECATED_BEFORE=0x50f02 -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_N [161/180] /usr/bin/x86_64-pc-linux-gnu-g++ -DKF_DEPRECATED_WARNINGS_SINCE=0x60000 -DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x56900 -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS_SINCE=0x60000 -DQT_DISABLE_DEPRECATED_BEFORE=0x50f02 -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_N [162/180] : && /usr/bin/x86_64-pc-linux-gnu-g++ -O2 -pipe -march=native -fno-diagnostics-color -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 -Werror FAILED: bin/vdv-cert-downloader : && /usr/bin/x86_64-pc-linux-gnu-g++ -O2 -pipe -march=native -fno-diagnostics-color -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 -Werror=init-self /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libphonenumber.so.8: undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >* absl::lts_20230802::log_internal::MakeCheckOpString<long, long>(long, long, char const* /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libphonenumber.so.8: undefined reference to `absl::lts_20230802::log_internal::LogMessageFatal::LogMessageFatal(char const*, int, absl::lts_20230802::string_view)' /usr/lib/gcc/x86_64-pc-linux-gnu/13/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libphonenumber.so.8: undefined reference to `google::protobuf::internal::LookUpEnumValue(google::protobuf::internal::EnumEntry const*, unsigned long, absl::lts_20230802::string_view, int*)' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-20231031-231524 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10 [2] x86_64-pc-linux-gnu-13 * clang/llvm (if any): clang version 17.0.4 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/17/bin Configuration file: /etc/clang/x86_64-pc-linux-gnu-clang.cfg /usr/lib/llvm/17 17.0.4 Python 3.11.6 Available Ruby profiles: [1] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.73.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 21.0.1_p12 [openjdk-bin-21] 2) Eclipse Temurin JDK 8.382_p05 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-21 system-vm The Glorious Glasgow Haskell Compilation System, version 9.2.8 php cli (if any): go version go1.21.3 linux/amd64 HEAD of ::gentoo commit 98a9e41e7c709c1d56da9ec49f864ba5c2013653 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Fri Nov 3 17:17:03 2023 +0000 2023-11-03 17:17:03 UTC emerge -qpvO kde-apps/kitinerary [ebuild R ] kde-apps/kitinerary-23.08.2 USE="-debug -doc -test"
Created attachment 873997 [details] emerge-info.txt
Created attachment 873998 [details] emerge-history.txt
Created attachment 873999 [details] environment
Created attachment 874000 [details] etc.clang.tar.xz
Created attachment 874001 [details] etc.portage.tar.xz
Created attachment 874002 [details] kde-apps:kitinerary-23.08.2:20231103-205319.log.xz
Created attachment 874003 [details] qlist-info.txt.xz
Created attachment 874004 [details] temp.tar.xz
Looks like i have the same problem in kitinerary-24.05.1.
I do not understand what exactly the problem is, but for me it seems to be solved by rebuilding dev-libs/libphonenumber (emerge -1 dev-libs/libphonenumber) and then installing/rebuilding kde-apps/kitinerary
I remember now, all makes sense, this is most likely this: /var/log/portage/elog/dev-libs:boost-1.85.0-r1:20240604-174150.log: LOG: postinst Boost.Regex is *extremely* ABI sensitive. If you get errors such as undefined reference to `boost::re_detail_108500::cpp_regex_traits_implementation <char>::transform_primary[abi:cxx11](char const*, char const*) const' Then you need to recompile Boost and all its reverse dependencies using the same toolchain. In general, *every* change of the C++ toolchain requires a complete rebuild of the Boost-dependent ecosystem. See for instance https://bugs.gentoo.org/638138 depends on it dev-libs/libphonenumber ... DEPEND=" dev-libs/icu:= dev-libs/protobuf:= dev-libs/boost:= " ...
