That's the actual culprit:
On 12/03/2024 13.33, JON Tauri wrote:
# LD [M] /var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.o
ld -m elf_x86_64 -z noexecstack --no-warn-rwx-segments -r -o
/var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.o
@/var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.mod ;
./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake
--ibt --orc --retpoline --rethunk --sls --static-call --uaccess --prefix=16
--link --module /var/lib/dkms/nvidia-current/525.147.05/build/nvidia-uvm.o
./tools/objtool/objtool: error while loading shared libraries: libelf.so.1:
cannot open shared object file: No such file or directory
make[4]: ***
[/usr/src/linux-headers-6.6.15-common/scripts/Makefile.build:443:
/var/lib/dkms/nvidia-current/525.147.05/build/nvidia.o] Error 127
make[4]: *** Deleting file
'/var/lib/dkms/nvidia-current/525.147.05/build/nvidia.o'
make[4]: *** Waiting for unfinished jobs....
This is not a bug in nvidia-kernel-dkms.
I assume this is a temporary breakage due to the ongoing 64-bit time_t
transition which involves a huge amount of package renames.
I cannot reproduce it in an up-to-date sid chroot with
linux-headers-6.6.15-amd64 installed (which has been superseded by 6.7.*
btw).
Updating your system again should probably fix the issue.
In case it persists: Which variant and version of the libelf.so.1
library do you have installed?
dpkg -l libelf1 libelf1t64
Andreas
