| In file included from ../igt-gpu-tools-1.26/lib/igt_aux.c:38: /usr/include/signal.h:198: note: this is the location of the previous definition 198 | #define sigev_notify_thread_id __sev_fields.sigev_notify_thread_id | ../igt-gpu-tools-1.26/lib/igt_aux.c: In function 'igt_sigiter_start': ../igt-gpu-tools-1.26/lib/igt_aux.c:181:20: error: 'struct sigevent' has no member named '_sigev_un' 181 | sev.sigev_notify_thread_id = __igt_sigiter.tid; | ^ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0_musl-j4-20221229-143533 ------------------------------------------------------------------- GNUMAKEFLAGS="$GNUMAKEFLAGS --shuffle" gcc-config -l: [1] x86_64-gentoo-linux-musl-12.2.0 * clang/llvm (if any): Python 3.10.9 Available Ruby profiles: [1] ruby27 (with Rubygems) [2] ruby31 (with Rubygems) * Available Rust versions: [1] rust-bin-1.66.0 [2] rust-1.66.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 17.0.5_p8 [openjdk-bin-17] Available Java Virtual Machines: [1] openjdk-bin-17 system-vm php cli (if any): [1] php8.2 * HEAD of ::gentoo commit e84042893535122ff0fa7a2bfb01bef00ccec1e5 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Fri Dec 30 07:17:05 2022 +0000 2022-12-30 07:17:04 UTC emerge -qpvO x11-apps/igt-gpu-tools [ebuild N ] x11-apps/igt-gpu-tools-1.26-r2 USE="-X -chamelium -doc -man -overlay -runner -tests -unwind (-valgrind) -xv" VIDEO_CARDS="amdgpu -intel -nouveau"
Created attachment 845818 [details] emerge-info.txt
Created attachment 845820 [details] emerge-history.txt
Created attachment 845822 [details] environment
Created attachment 845824 [details] etc.portage.tar.bz2
Created attachment 845826 [details] logs.tar.bz2
Created attachment 845828 [details] temp.tar.bz2
Created attachment 845830 [details] x11-apps:igt-gpu-tools-1.26-r2:20221230-080124.log
Is this still a problem with v1.27.1?
(In reply to Matt Turner from comment #8) > Is this still a problem with v1.27.1? no
*** Bug 876469 has been marked as a duplicate of this bug. ***
*** Bug 833033 has been marked as a duplicate of this bug. ***
