On 2014-03-11 10:26, Nils Rennebarth wrote: > On 11.03.2014 08:25, Felix Fietkau wrote: >> My guess is that you have module symbol versioning turned on in your >> kernel config for ppc. > Correct > >> This is incompatible with OpenWrt builds, because >> OpenWrt always builds the kernel modules before the image. > Could requirements like that be noted in a prominent place. With a good > suggestion what this "prominent place" is, I would even do that myself. It may be better to send a patch to make the build fail early with a descriptive error message.
> However, I always thought, CONFIG_MODVERSIONS was a good idea, especially when > building development kernels where it protects you from loading a module which > is incompatible with the currently running kernel, so I would very much keep > support for symbol versioning. In OpenWrt we have package dependencies taking care of incompatibilities. The virtual 'kernel' package has a hash of the kernel config in the version, and any module packages depend on that. This makes CONFIG_MODVERSIONS unnecessary. > What about building modules by removing vmlinux and System.map, and then > calling > make vmlinux modules We don't want to build the kernel twice. - Felix _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
