Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.13.0-1006-raspi -C /lib/modules/5.13.0-1006-raspi/build M=/var/lib/dkms/adv-17v35x/5.0.6.0-1/build....
cleaning build area...
DKMS: build completed.
Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.13.0-14-generic -C /lib/modules/5.13.0-14-generic/build M=/var/lib/dkms/adv-17v35x/5.0.6.0-1/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.13.0-14-generic (armv7l)
Because the toolchain fix was only applied in the linux-raspi flavour so far
, and not generic.
I.e. gcc-11 did not migrate, and "UBUNTU: SAUCE: arm: Fix instruction set selection for GCC 11" is not in generic kernel, yet.
so it is expected that dkms builds for generic kernel fail on armhf with gcc-11 from impish-release.
@juerg
From your autopkgtest result:
Building module: 5.13.0- 1006-raspi -C /lib/modules/ 5.13.0- 1006-raspi/ build M=/var/ lib/dkms/ adv-17v35x/ 5.0.6.0- 1/build. ...
cleaning build area...
make -j4 KERNELRELEASE=
cleaning build area...
DKMS: build completed.
Building module: 5.13.0- 14-generic -C /lib/modules/ 5.13.0- 14-generic/ build M=/var/ lib/dkms/ adv-17v35x/ 5.0.6.0- 1/build. ...(bad exit status: 2)
cleaning build area...
make -j4 KERNELRELEASE=
Error! Bad return status for module build on kernel: 5.13.0-14-generic (armv7l)
Because the toolchain fix was only applied in the linux-raspi flavour so far
, and not generic.
I.e. gcc-11 did not migrate, and "UBUNTU: SAUCE: arm: Fix instruction set selection for GCC 11" is not in generic kernel, yet.
so it is expected that dkms builds for generic kernel fail on armhf with gcc-11 from impish-release.