Zitat von: /var/lib/dkms/nvidia-legacy-340xx/340.98/build/make.logtest -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p ./../.tmp_versions ; rm -f ./../.tmp_versions/*
make -f ./scripts/Makefile.build obj=./..
scripts/Makefile.build:44: ../Makefile: Datei oder Verzeichnis nicht gefunden
make[3]: *** Keine Regel, um ,,../Makefile" zu erstellen. Schluss.
Makefile:1472: die Regel für Ziel ,,_module_./.." scheiterte
make[2]: *** [_module_./..] Fehler 2
make[2]: Verzeichnis ,,/usr/src/linux-headers-4.8.2-towo.1-siduction-amd64" wird verlassen
Makefile:193: die Regel für Ziel ,,nvidia.ko" scheiterte
make[1]: *** [nvidia.ko] Fehler 2
make[1]: Verzeichnis ,,/var/lib/dkms/nvidia-legacy-340xx/340.98/build" wird verlassen
Makefile:219: die Regel für Ziel ,,../Module.symvers" scheiterte
My fault or something with the new kernel?
It's not the kernel, it's the today update of gcc-6 (2.6.0-7). If you downgrade all gcc related packages to the testing version (2.6.0-6) all is working fine,
Btw, it's not only nvidia, it seems all 3rd party modules like vbox, vmware, nvidia and so on, will not build.
By now there is a new kernel as well, so no need to downgrade all these packages
Seems to be quite a few changes coming lately.
Good to see, but also a time for caution when dist-upgrading.
Quick question Towo.
If the critter in your signature not a bug, is it a feature? :-)
Well, we are moving up to freeze. So everryone tries to get changes in in a rush, which is not always good for quality.
Right, that explains the flurry of activity then.
Thanks Devil.