[OpenWrt-Devel] kernel changes on recompilation?
codemarauder at gmail.com
Wed Oct 1 22:04:51 EDT 2014
On 2 October 2014 04:45:38 GMT+05:30, Gui Iribarren <gui at altermundi.net> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>On 01/10/14 14:31, Baptiste Jonglez wrote:
>> When you activate/deactivate packages in menuconfig, it may modify
>> what gets compiled into the kernel, to add/remove support for the
>> various subsystems needed by the packages you build. This will
>> cause the kernel to be rebuilt with a different package number.
>> If you just rebuild the image without changing anything in
>> menuconfig, I think the kernel package will not be rebuilt. Not
>> sure though, just try and see for yourself :)
>Hm.. i can contribute a datapoint: if you make a "dirclean", without
>changing anything in the makeconfig or anything else
>(say, "make dirclean ; make ; make dirclean; make")
>you'll end up with two different kernel-hashes (after step 2 and 4)
>so there's (in addition to selected-kernel-features and such) some
>kind of build-date being taken into account for calculating the hash,
>which gets lost when doing dirclean, somewhere inside build_dir i
I never did a clean or dir clean but yes I enabled a few packages and modules with new requirements.
Which is fine by my own thinking. And just for adding e.g. batman-adv to existing devices in the field, it becomes a pain to reflash them due to kernel hash change.
Any more pointers please?
>> On Wed, Oct 01, 2014 at 03:43:20PM +0530, Nishant Sharma wrote:
>>> Hello members,
>>> Although, I am compiling and using custom OpenWRT images since 8
>>> months now, but I am still confused with this particular
>>> behaviour. I am using it primarily on x86 Alix & APU devices.
>>> Everytime I run a make and kernel gets recompiled, it changes
>>> the hex value appended to the kernel package name which makes a
>>> lot of packages or new modules compiled uninstallable on
>>> existing systems through opkg.
>>> What is the best practice for doing these kind of things or is
>>> there any workaround?
>>> Thanks in advance.
>>> Regards, Nishant _______________________________________________
>>> openwrt-devel mailing list openwrt-devel at lists.openwrt.org
>>> _______________________________________________ openwrt-devel
>>> mailing list openwrt-devel at lists.openwrt.org
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.12 (GNU/Linux)
>-----END PGP SIGNATURE-----
>openwrt-devel mailing list
>openwrt-devel at lists.openwrt.org
Sent from my Android device with K-9 Mail. Please excuse my brevity.
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel