From: Arthur Marsh <arthur.marsh@internode.on.net>
To: x86@kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, x86@kernel.org
Subject: Cross-comilation from amd64 to i686 - issue with /usr/src/linux/arch/x86/boot/tools/build
Date: Mon, 13 Sep 2021 23:54:15 +0930 [thread overview]
Message-ID: <000ef85f-9326-706e-007b-4549901797d7@internode.on.net> (raw)
Hi, I had a problem when doing a Linux kernel cross compile from amd64
to i386/i686 a few days ago which I solved quickly, but wonder if the
issue points to a problem:
/usr/src/linux/arch/x86/boot/tools/build had (apparently) been compiled
over a year earlier when I was running under amd64 without multilib
support, when I installed the i386/i686 gcc-11 under amd64, and
attempted to cross-compile the kernel for i386, I received an error
about bzImage:
BUILD arch/x86/boot/bzImage
make[5]: *** [arch/x86/boot/Makefile:84: arch/x86/boot/bzImage] Error 139
make[5]: *** Deleting file 'arch/x86/boot/bzImage'
make[4]: *** [arch/x86/Makefile:273: bzImage] Error 2
Once I removed the old /usr/src/linux/arch/x86/boot/tools/build binary
and re-ran the kernel build, a new "build" binary was built and the
kernel build process succeeded and the built kernels ran fine on my
i386/i686 system.
I'm not sure if running a cross-compile from amd64 to i386 for the first
time or in fact any update of the host CC or cross-compiler CC should
have triggered a recompilation of /usr/src/linux/arch/x86/boot/tools/build.c
Kernel build command for the cross-compilation was:
make ARCH=i386 CROSS_COMPILE=i686-linux-gnu- CC=i686-linux-gnu-gcc-11
-j6 menuconfig bindeb-pkg
Arthur.
reply other threads:[~2021-09-13 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000ef85f-9326-706e-007b-4549901797d7@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®