too long lines were shrinked: [333/343] /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_ATOMIC_DYN_LINK -DBOOST_ATOMIC_NO_LIB -DBOOST_CONTEXT_DYN_LINK -DBOOST_CONTEXT_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_FILESYSTEM_NO_LIB -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB -DBOOST_REGEX_DYN_LINK -DBOOST_REGEX_NO_LIB - [334/343] /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_ATOMIC_DYN_LINK -DBOOST_ATOMIC_NO_LIB -DBOOST_CONTEXT_DYN_LINK -DBOOST_CONTEXT_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_FILESYSTEM_NO_LIB -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB -DBOOST_REGEX_DYN_LINK -DBOOST_REGEX_NO_LIB - [335/343] /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_ATOMIC_DYN_LINK -DBOOST_ATOMIC_NO_LIB -DBOOST_CONTEXT_DYN_LINK -DBOOST_CONTEXT_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_FILESYSTEM_NO_LIB -DBOOST_NO_AUTO_PTR -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_NO_LIB -DBOOST_REGEX_DYN_LINK -D [336/343] : && /usr/bin/x86_64-pc-linux-gnu-g++ -fPIC -O2 -pipe -march=native -fno-diagnostics-color -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -flto -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,--defsym=__gentoo_check_ldflags__=0 -Werror=lto-type-mismatch -Werror=stri FAILED: libfolly.so.0.58.0-dev : && /usr/bin/x86_64-pc-linux-gnu-g++ -fPIC -O2 -pipe -march=native -fno-diagnostics-color -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -flto -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,--defsym=__gentoo_check_ldflags__=0 -Werror=lto-type-mismatch -Werror=strict-aliasin /var/tmp/portage/dev-cpp/folly-2024.11.04.00-r2/work/folly-2024.11.04.00/folly/io/async/EpollBackend.h:34:7: error: type struct EpollBackend violates the C++ One Definition Rule [-Werror=odr] 34 | class EpollBackend : public EventBaseBackendBase { | ^ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_systemd-20250205-213502 UNMASKED: Requested by sam =media-video/ffmpeg-7* <sys-devel/gcc-15.0.9999:15 Please re-assign to ztrawhcse@ if you cannot reproduced it with regular meson. <dev-build/meson-9999 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-15 * clang version 19.1.7 llvm-config: 19.1.7 Python 3.12.9 go version go1.23.6 linux/amd64 [1] php8.2 * [2] php8.3 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.84.1 [2] rust-1.84.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.26_p4 [openjdk-bin-11] 2) Eclipse Temurin JDK 17.0.14_p7 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.6_p7 [openjdk-bin-21] 4) Eclipse Temurin JDK 8.442_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 [4] openjdk-bin-21 system-vm HEAD of ::gentoo commit f8a24333e7439a603a7eddf2934cb90acf0dbd3d Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Feb 11 07:34:32 2025 +0000 2025-02-11 07:34:31 UTC emerge -qpvO =dev-cpp/folly-2024.11.04.00-r2 [ebuild N ] dev-cpp/folly-2024.11.04.00-r2 USE="-llvm-libunwind -test"
Created attachment 918684 [details] emerge-info.txt
Created attachment 918685 [details] dev-cpp:folly-2024.11.04.00-r2:20250211-085950.log.xz
Created attachment 918686 [details] emerge-history.txt
Created attachment 918687 [details] environment
Created attachment 918688 [details] etc.clang.tar.xz
Created attachment 918689 [details] etc.portage.tar.xz
Created attachment 918690 [details] logs.tar.xz
Created attachment 918691 [details] qlist-info.txt.xz
Created attachment 918692 [details] temp.tar.xz
Hit this on GCC 14. Attempted a version bump - still happens in 2025.02.17.00. Logged a ticket upstream.
Can no longer reproduce with gcc 15.0.1_pre20250418 on Folly 2025.04.14.00. Will close with version bump.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=405f0da22d8cad059006ebbdef648d1a968a075f commit 405f0da22d8cad059006ebbdef648d1a968a075f Author: sin-ack <sin-ack@protonmail.com> AuthorDate: 2025-04-21 15:58:12 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-04-22 01:15:22 +0000 dev-cpp/folly: add 2025.04.14.00 io_uring support is temporarily disabled because they depend on features that haven't even been released in liburing yet. Closes: https://bugs.gentoo.org/949607 Ref: https://github.com/facebook/folly/issues/2420 Signed-off-by: sin-ack <sin-ack@protonmail.com> Signed-off-by: Sam James <sam@gentoo.org> dev-cpp/folly/Manifest | 1 + .../folly-2025.04.14.00-force-liburing-off.patch | 27 +++++ dev-cpp/folly/folly-2025.04.14.00.ebuild | 121 +++++++++++++++++++++ 3 files changed, 149 insertions(+)
*** Bug 954800 has been marked as a duplicate of this bug. ***
(In reply to sin-ack from comment #11) > Can no longer reproduce with gcc 15.0.1_pre20250418 on Folly 2025.04.14.00. > Will close with version bump. Did you use -flto=* -Werror=XXX? (See bug 954800).
Just hit this on `dev-cpp/folly-2025.04.14.00-r1`; confirmed - still an issue. You will need to set the LTO error options that Sam linked to, or https://wiki.gentoo.org/wiki/LTO#Enable_LTO (you can use p.env to enable for specific packages if desired).
