On 13.1.2013 16:14, Mark Constable wrote:
> On 13/01/13 23:54, darius wrote:
>> Ok, first I've done 'make kernel_menuconfig' then made 'make
>> menuconfig', but still didn't find kernel modules I enabled. Then I
>> ran 'make V=99 > build.log'. Everythign went ok, but module wasn't
>> in the kernel. Then I've inspected build.log and found that my
>> module 'xt_addrtype' was selected with 'M' means build as package
>> despite the fact that I selected it with yes ('*') in
>> kernel_menuconfig. So now I have right module compiled, but as
>> standalone. I'd like to have it in kernel. how can I do that ?
>
> I could be way off but this is something I would try, at least...
>
> grep -i addrtype .config
>
> and see if there is anything in the main config file that looks like
> it might have something to do with what you want. If an entry looks
> promising then edit the file, search for that entry and manually
> change it to SOMETHING=y. Run "make oldconfig" then make again.
>
> I'm not sure where the actual kernel .config file would be and that
> would be a better place to try but it may also be in the main
> .config so worth a try. Hopefully someone with a real clue will
> correct my naive suggestion.
>
Hi,
as far as my limited understanding of the build process reaches, you
need to run "make menuconfig" first, as that's where you specify the
platform, which brings in the default kernel configuration. You can then
run "make kernel_menuconfig" and customize the kernel. But if you run
menuconfig again, your changes can get overwritten with the platform
defaults.
Hope this helps.
Regards
Tomas
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-users
