Summary: | Genkernel should recompile Busybox if cflags have changed. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nathan Dehnel <ncdehnel> |
Component: | Current packages | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nathan Dehnel
2016-05-14 05:39:45 UTC
In this case, the user should be clearing the genkernel cache. Changing arch/cflags incompatibly is not the only thing that would cause the cached copy to be unusable, and short of adding lots of tracking info to the cached files, I'm not sure there is any easy ways of catching this. I am closing this as obsolete because with genkernel-4.0.0-beta.1 and later, cross-compile support was reworked and bug is mentioning especially that. I.e. when you start creating kernel for x86_64 and will now start to build kernel for arm64, you will get new packages. Of course we still use general CFLAGS (like portage) which you can set via --utils-cflags. There's no need to mess with that setting (they shouldn't contain --march). But if you do, you must rebuild on your like you have to do for packages in Gentoo. |