[OpenWrt-Devel] kernel changes on recompilation?

[Nishant Sharma]

On 2 October 2014 04:45:38 GMT+05:30, Gui Iribarren <gui at altermundi.net> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>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
>suppose.

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?

Regards,
Nishant

>
>cheers!
>
>gui
>
>> 
>> Baptiste
>> 
>> 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 
>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>> 
>>> 
>>> _______________________________________________ openwrt-devel 
>>> mailing list openwrt-devel at lists.openwrt.org 
>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.12 (GNU/Linux)
>
>iQIcBAEBAgAGBQJULIsaAAoJEIJqNBvBfxrIX9wQAI987g9ibT2DYo2LoTdGKjrt
>1w6m8AHT5xAKLJRlbOLZ0eDeArtryOh+s+rZzOdSAd/++Yh/8cjx3KlX6rI0tqQY
>cTW49Ghbm23VZaPhIq86y3pJOYN1VdYhk/ZYR4hTHER1lJwiJYl/Ikrhb4X7mhFv
>m2NXwye+aIAruXlTo4MJ5hGYxxV5XgeAtwgtuaZDW8MtkxBIiNceSziOyaoU6mC0
>DBuslTnwNqZbkGoqRuZlkzJRjTtqKtG1CbkDRk9jWJmAhXCfEve5zqkI0wB5dwIi
>c1F7/+a4SKW8iEQLEDELPEFqW/8rSO5QJL7O+d98LqO/b7kJiYuRfsAeMAdITMGD
>TX4WPHyE47LSP5DdVolEOkX9YBwRMVFEiC594/unsHx7186k3h/84I0ZYtCs6WBo
>106AuOzxcktnLycPPvR4Gj2pUbY0cGMeTgD+Z5+1sBAFDgKMwqUmVGy5NxCFQ39I
>Va1z0ihqVey1+Bh3YJ86mJ6L02kdaEvc7+vpbtdJnXSRQGSjSK8wmvNjzCkvslJO
>d3aQa39urJAgZ/flfk+SPvU1ZTr1ohjsmzcCwMq2KZFdr7wcBcQE2YZ1b77UhUcl
>jdDqGaSUFbjy504UpQaGscjMwZctwT8IWcbePnBsutlNue0a5A1kVnhQoSgPeFCi
>hxPIp54tbwYZ41YvJyPb
>=HY70
>-----END PGP SIGNATURE-----
>_______________________________________________
>openwrt-devel mailing list
>openwrt-devel at lists.openwrt.org
>https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel