From: Hustler One via Grub-devel <grub-devel@gnu.org>
To: Grub Devel <grub-devel@gnu.org>
Cc: nine-ball@tutanota.com
Subject: Re: Re: [PATCH v2 1/1] Check linker for --image-base support
Date: Sun, 18 Jan 2026 13:14:27 +0100 (CET) [thread overview]
Message-ID: <OjG0mlH--F-9@tutanota.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 492 bytes --]
I can confirm myself that this patch does the complete opposite of what it tries to achieve.
I had to revert the commit when updating GRUB to 2.14 on [nixpkgs](https://github.com/NixOS/nixpkgs/pull/481112).
Also, Leah Rowe has also done the same on [Libreboot](https://codeberg.org/libreboot/lbmk/src/branch/master/config/grub/nvme/patches/0010-Revert-configure-Check-linker-for-image-base-support.patch
).
For me, at least, behavior was universally broken on both clang (LLVM21) and GCC.
[-- Attachment #1.2: Type: text/html, Size: 1095 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
reply other threads:[~2026-01-18 13:57 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=OjG0mlH--F-9@tutanota.com \
--to=grub-devel@gnu.org \
--cc=nine-ball@tutanota.com \
/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