On 2016-01-05 5:12 PM, Megha Dey wrote:
When qemux86 is selected as MACHINE type, and a custom linux kernel
is built, yocto assumes KARCH to be x86. This leads to a 64 bit
config file getting generated instead of a 32 bit one. Hence, always
make KARCH as i386 when a 32 bit MACHINE type is selected.
Signed-off-by: Megha Dey <[email protected]>
---
tools/configme | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/configme b/tools/configme
index 903b3c1..9651280 100755
--- a/tools/configme
+++ b/tools/configme
@@ -201,6 +201,9 @@ run_board_config()
if [ $KARCH == "mips64" ]; then
KARCH=mips
fi
+ if [ $KARCH == "x86" ]; then
+ KARCH=i386
i386 is obsolete, and x86 should be used with the appropriate
32 bit configs.
I purged all i386 references quite some time ago, since they
can trigger other subtle errors.
Can you elaborate on what exactly what you are building, and
what fragments are in play that a 64 bit kernel is being
generated incorrectly ? We always go out of our way to specify
32 or 64 bit for that reason.
Bruce
+ fi
if [ -z "$BUILD_DIR" ]; then
echo No build dir specified. Use \"-o\" to specify one.
--
_______________________________________________
linux-yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/linux-yocto
