i386 machine.cfg: Explicitly disable 64BIT
PATCH 1/1 i386 machine.cfg: Explicitly disable 64BIT
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.
Similar to e9ec769926b2378e63380bd7762ce7ce201af151 in the yocto-kernel-cache repo
--- .../substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg | 3 +++ 1 file changed, 3 insertions(+)
scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg +3 -0
@@ -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
Signature · 1 line
2.7.4
✗ patchtest: failure for i386 machine.cfg: Explicitly disable 64BIT
== Series Details ==
Series: i386 machine.cfg: Explicitly disable 64BIT
Revision: 1
URL : https://patchwork.openembedded.org/series/6088/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at 6d6d0737a2)
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe