All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mikhail B. WproxyM" <w.proxy.m@gmail.com>
To: grub-devel@gnu.org
Subject: Fwd: boot/grub2: grub-core-build-fixes-for-i386 (grub-2.04 + binutils-2.35.2 + pseudo-op .code64)
Date: Wed, 5 May 2021 12:39:53 +0300	[thread overview]
Message-ID: <CANTg=QgWdsyQJqA43txuS_wsrYcJt0UVQsfS-d_1Q59oKkWL9w@mail.gmail.com> (raw)
In-Reply-To: <CANTg=Qj3vMern005jEMmUs2dWvi0oJ9Y3aoS4ocsrD91KoXW5Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

We are using binutils-2.35.2+ (later then 2.29.1), grub-2.04,
cross-compiling on recent buildroot under i386/i686 and getting error:

> lib/i386/relocator64.S:66: Error: unknown pseudo-op: `.code64'

So, the working patch is attached. Please add it to grub2.

Sources:
1) https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41982 (Jul 2020)
2) http://archive.linuxfromscratch.org/mail-archives/lfs-support/2018-January/051723.html

--
Best regards

[-- Attachment #2: 0150-grub-core-build-fixes-for-i386.patch --]
[-- Type: application/x-patch, Size: 1722 bytes --]

  parent reply	other threads:[~2021-05-05 13:29 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
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 ` Mikhail B. WproxyM [this message]
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='CANTg=QgWdsyQJqA43txuS_wsrYcJt0UVQsfS-d_1Q59oKkWL9w@mail.gmail.com' \
    --to=w.proxy.m@gmail.com \
    --cc=grub-devel@gnu.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 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.