Hi Andreas, Andreas Beckmann wrote: > That error is very cryptic ... so let's run dkms manually
Ack. > Check for working gcc: No > ! You need gcc to install module from source [...] > Oh, your package insists on building the kernel module with gcc instead of > getting the correct compiler (i.e. the same versioned gcc-X that was used to > build the kernel and that is depended upon by the kernel header package used) > from kbuild. A kernel module built with a different compiler version than the > kernel itself may not work. The kernel is not neccessarily built with the > same compiler version as gcc points to. Correct. But how do I determine that kernel-specific compiler without tracking down package dependencies? linux-compiler-gcc-10-x86 seems not to provide a symlink or similar. → dpkg -L linux-compiler-gcc-10-x86 /. /usr /usr/share /usr/share/doc /usr/share/doc/linux-compiler-gcc-10-x86 /usr/share/doc/linux-compiler-gcc-10-x86/changelog.Debian.gz /usr/share/doc/linux-compiler-gcc-10-x86/copyright Or is tracking down package dependencies the way to go? Actually I would have expected that DKMS already takes care of this. Because I deliberately added this patch to avoid this situation: -CC = gcc +CC ?= gcc > There are more dkms packages looking for a proper solution for this problem: > openafs-modules-dkms (#945506) > zfs-dkms (#946497) I see. Thanks! Doesn't look very promising though. > Please depend on gcc if you cannot find a way to use the kernel > compiler. Actually I thought that DKMS does this already, but I see that _any_ C compiler can fulfil it's dependency. Hrm. > You cannot expect build-essential to be available. Correct. But that's also not needed, given dkms' dependencies. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE