too long lines were shrinked: [96/155] /usr/bin/x86_64-pc-linux-musl-g++ -DHAVE_LIBLZMA -I/usr/src/linux -I/usr/lib/llvm/18/include/../tools/clang/include -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0_build/src/cc -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0/src/cc -I/var/tmp/portage/dev-util/bcc-0.31.0/work/b [97/155] /usr/bin/x86_64-pc-linux-musl-g++ -DEXPORT_USDT -DHAVE_EXTERNAL_LIBBPF -DHAVE_LIBLZMA -I/usr/src/linux -I/usr/lib/llvm/18/include/../tools/clang/include -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0/src -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0_build/src -I/var/tmp/por [98/155] : && /usr/bin/cmake -E rm -f src/cc/libbcc.a && /usr/bin/x86_64-pc-linux-musl-ar qc src/cc/libbcc.a src/cc/api/CMakeFiles/api-objects.dir/BPF.cc.o src/cc/api/CMakeFiles/api-objects.dir/BPFTable.cc.o src/cc/frontends/clang/CMakeFiles/clang_frontend-objects.dir/loader.cc.o src/cc/frontends/c [99/155] /usr/bin/x86_64-pc-linux-musl-g++ -DHAVE_LIBLZMA -I/usr/src/linux -I/usr/lib/llvm/18/include/../tools/clang/include -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0_build/src/cc -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0/src/cc -I/var/tmp/portage/dev-util/bcc-0.31.0/work/b FAILED: examples/cpp/CMakeFiles/KModRetExample.dir/KModRetExample.cc.o /usr/bin/x86_64-pc-linux-musl-g++ -DHAVE_LIBLZMA -I/usr/src/linux -I/usr/lib/llvm/18/include/../tools/clang/include -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0_build/src/cc -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0/src/cc -I/var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0 /var/tmp/portage/dev-util/bcc-0.31.0/work/bcc-0.31.0/examples/cpp/KModRetExample.cc:23:10: fatal error: error.h: No such file or directory 23 | #include <error.h> | ^~~~~~~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_musl_hardened-20240906-211007 UNMASKED: Please re-assign to toolchain@ if you get a test failure in C, C++, or Fortran code which makes no sense. /etc/portage/package.unmask/60gcc:<sys-devel/gcc-15.0.9999:15 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-musl-15 * clang/llvm (if any): clang version 18.1.8 Target: x86_64-pc-linux-musl Thread model: posix InstalledDir: /usr/lib/llvm/18/bin Configuration file: /etc/clang/x86_64-pc-linux-musl-clang.cfg /usr/lib/llvm/18 18.1.8 Python 3.12.6 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.80.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.24_p8 [openjdk-bin-11] 2) Eclipse Temurin JDK 17.0.12_p7 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.4_p7 [openjdk-bin-21] Available Java Virtual Machines: [1] openjdk-bin-11 [2] openjdk-bin-17 [3] openjdk-bin-21 system-vm php cli (if any): go version go1.23.0 linux/amd64 HEAD of ::gentoo commit c62e4e3a0b578b79536b12ff9289993d49e69997 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Sep 10 21:50:53 2024 +0000 2024-09-10 21:50:53 UTC emerge -qpvO =dev-util/bcc-0.31.0 [ebuild N ] dev-util/bcc-0.31.0 USE="lua python -static-libs -test" LLVM_SLOT="18 -15 -16 -17" LUA_SINGLE_TARGET="luajit" PYTHON_TARGETS="python3_12 -python3_10 -python3_11 -python3_13"
Created attachment 902606 [details] emerge-info.txt
Created attachment 902607 [details] dev-util:bcc-0.31.0:20240910-224201.log
Created attachment 902608 [details] emerge-history.txt
Created attachment 902609 [details] environment
Created attachment 902610 [details] etc.clang.tar.xz
Created attachment 902611 [details] etc.portage.tar.xz
Created attachment 902612 [details] qlist-info.txt.xz
Created attachment 902613 [details] temp.tar.xz
Simple fix (see linked upstream bug/comment): diff --git a/dev-util/bcc/bcc-0.31.0.ebuild b/dev-util/bcc/bcc-0.31.0.ebuild index 274d6f9b7..4f5071766 100644 --- a/dev-util/bcc/bcc-0.31.0.ebuild +++ b/dev-util/bcc/bcc-0.31.0.ebuild @@ -102,6 +102,9 @@ src_prepare() { mv "${script}" "tools/old/old-${script##*/}" || die done + # bug 939453 + sed -i '/#include <error.h>/d' examples/cpp/KModRetExample.cc || die + use static-libs || PATCHES+=( "${FILESDIR}/bcc-0.31.0-dont-install-static-libs.patch" ) # use distutils-r1 eclass funcs rather than letting upstream handle python
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=80637f03d8c6f0cc71efa1139c4d4098e2a49a77 commit 80637f03d8c6f0cc71efa1139c4d4098e2a49a77 Author: Patrick McLean <chutzpah@gentoo.org> AuthorDate: 2024-09-11 17:22:03 +0000 Commit: Patrick McLean <chutzpah@gentoo.org> CommitDate: 2024-09-11 17:30:05 +0000 dev-util/bcc: restore tool symlinking, add missing deps, musl fix - Restore tool symlinking, making sure to skip python tools - Add some logic to tool symlinking to avoid collisions - Prefix tool name for some more generically named tools with bcc- - Add some missing dependencies (libffi, zstd, ncurses[tinfo], flex, bison) - Add lzma USE flag and remove automagic dep - Restore musl fix that somehow got lost (bug #939453) Closes: https://bugs.gentoo.org/939453 Signed-off-by: Patrick McLean <chutzpah@gentoo.org> .../{bcc-0.31.0-r1.ebuild => bcc-0.31.0-r2.ebuild} | 55 +++++++++++++++++++--- .../bcc/files/bcc-0.31.0-no-automagic-deps.patch | 15 ++++++ 2 files changed, 63 insertions(+), 7 deletions(-)
