From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] boot/grub2: grub-core-build-fixes-for-i386 (grub-2.04 + binutils-2.35.2 + pseudo-op .code64)
Date: Wed, 28 Apr 2021 13:44:09 +0200 [thread overview]
Message-ID: <20210428134409.24999483@windsurf> (raw)
In-Reply-To: <CANTg=Qig12wrSU2WUBPmXFkjSpmmTo1gfEn1x6rgDR8vTM-82g@mail.gmail.com>
Hello Mikhail,
On Wed, 28 Apr 2021 11:07:13 +0300
"Mikhail B. WproxyM" <w.proxy.m@gmail.com> wrote:
> I have the build error, when building *from i686* to i686.
>
> You do not have the build error, when building *from x86-64* to i686.
> Looks like it is the reason.
>
> Grub2 developers do not run build tests under i386/i686. Even you do
> not run build tests under i686.
I was worried the issue would be related from the difference of the
build machine architecture. In theory it shouldn't matter, as the file
being built is built with the cross-compiler, but it seems like there
is an actual difference.
What about having this patch submitted to upstream Grub ?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-04-28 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 9:35 [Buildroot] boot/grub2: grub-core-build-fixes-for-i386 (grub-2.04 + binutils-2.35.2 + pseudo-op .code64) Mikhail B. WproxyM
2021-04-26 20:56 ` Thomas Petazzoni
2021-04-28 8:07 ` Mikhail B. WproxyM
2021-04-28 11:44 ` Thomas Petazzoni [this message]
2021-04-28 13:23 ` Mikhail B. WproxyM
2021-05-13 7:19 ` Mikhail B. WproxyM
2021-05-13 7:19 ` Mikhail B. WproxyM
2021-05-13 7:28 ` John Paul Adrian Glaubitz
2021-05-05 9:39 ` Fwd: " Mikhail B. WproxyM
2021-05-05 9:44 ` Mikhail B. WproxyM
2021-05-05 16:33 ` Daniel Kiper
2021-05-13 10:35 ` Jan Nieuwenhuizen
2021-05-17 16:49 ` Daniel Kiper
2021-05-18 5:05 ` Jan Nieuwenhuizen
2021-05-18 7:02 ` John Paul Adrian Glaubitz
2021-05-05 14:16 ` Fwd: " John Paul Adrian Glaubitz
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=20210428134409.24999483@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.