On Thu, 2017-03-30 at 09:56 -0700, Saul Wold wrote: > Since we do not set the 64 bit flags, newer kernels seem to build 64bit > config files by default. This is due to a hard-coded uname -m check that > selects the KBUILD_DEFCONFIG based on the host, not the cross target. >
Saul, this is poky code, so wrong list. > Similar to e9ec769926b2378e63380bd7762ce7ce201af151 in the yocto-kernel-cache > repo > > [YOCTO #11230] > > Signed-off-by: Saul Wold <s...@linux.intel.com> > --- > .../substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg | 3 > +++ > 1 file changed, 3 insertions(+) > > diff --git > a/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg > > b/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg > index 3b168b7..fe5b882 100644 > --- > a/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg > +++ > b/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg > @@ -1,5 +1,8 @@ > # yocto-bsp-filename {{=machine}}.cfg > CONFIG_X86_32=y > +# Must explicitly disable 64BIT > +# CONFIG_64BIT is not set > + > CONFIG_MATOM=y > CONFIG_PRINTK=y > > -- > 2.7.4 > -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto