On Mon, 2016-03-21 at 11:52 +0000, Ben Hutchings wrote: > On Mon, 2016-03-21 at 11:06 +0000, Ian Campbell wrote: > > > > On Mon, 2016-03-21 at 11:31 +0100, JM wrote: > > > > > > > > > Hi, > > > > > > The system is a qnap, kirkwood flavour. > > > > > > I would previously build vanilla kernels with Debian's .config as > > > described in the Kernel Handbook (copy old config, make > > > oldconfig, > > > make deb-pkg) and that worked well as of 4.4.1-1-exp1. > > > > > > Yesterday I updated my system (including debian's kernel from > > > testing), downloaded vanilla 4.4.6 source and to my surprise make > > > deb-pkg ended up producing an uninstallable armhf build. Is this > > > somehow related to kirkwood->marvell transition? > > I think it is related to: > > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/comm > > it > > /?id=63a478fbc05cb0627b0a33a69f3aed8dcb965953 > > and the fact that the armel/marvell flavour has CONFIG_VFP set now > > which breaks the heuristic used there. > [...] > > Oops, I suppose it should be checking the architecture version too.
Hopefully checking ARCH_MULTI_* would be sufficient, rather than needing to list all the (many many) CPU_*. That relies on a sufficient number of platforms being multi arch enabled, IIRC all v7 ones are now, so lack of an ARCH_MULTI_* would indicate arm or armel I suppose. Ian.
