[Added Nicolas, for whom this all might be painfully obvious.] On Wed, 2016-11-30 at 18:40 -0500, Jarod Wilson wrote: > My config had MODVERSIONS set, yes.
For the record triggering this flood of ERRORs for undefined symbols that you ran into has been possible ever since TRIM_UNUSED_KSYMS was added to the tree (in v4.7). I just tested that. Perhaps this is all documented somewhere. But even then it would be nice if the build would fail right at the start. Ie, the build probably should fail if one does "make bzImage" while having a .config with CONFIG_TRIM_UNUSED_KSYMS=y CONFIG_MODULES=y # CONFIG_MODVERSIONS is not set Because it seems in that case the subsequent "make modules" will then end in this flood of ERRORs. Paul Bolle