From: slymattz <slymattz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: binutils update breaks refind
Date: Mon, 11 Mar 2024 12:23:29 +0100 [thread overview]
Message-ID: <20240311112329.255A02B739@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49170@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
New comment by slymattz on void-packages repository
https://github.com/void-linux/void-packages/issues/49170#issuecomment-1988214496
Comment:
Let me recap this bug report.
Context:
https://lists.gnu.org/archive/html/info-gnu/2022-02/msg00009.html
**GNU Binutils 2.38**
```
* Support for efi-app-aarch64, efi-rtdrv-aarch64 and
efi-bsdrv-aarch64 has been added to objcopy in order to enable
UEFI development using binutils.
```
Solution by @sgn (see @@ -148,8 +140,10 @@):
https://github.com/void-linux/void-packages/blob/8f60d7410c76cd192636349b19231eb07a082e4c/srcpkgs/refind/patches/add-cross-compile-support-and-fix-binutils-aarch64.patch
Successful workflow aarch64 builds after applying the patch:
```
/usr/bin/aarch64-linux-gnu-objcopy -j .text -j .sdata -j .data -j .dynamic -j .dynsym -j .rel \
-j .rela -j .rel.* -j .rela.* -j .rel* -j .rela* \
-j .reloc --target=efi-app-aarch64 refind_aa64.so refind_aa64.efi
```
```
/usr/bin/aarch64-linux-musl-objcopy -j .text -j .sdata -j .data -j .dynamic -j .dynsym -j .rel \
-j .rela -j .rel.* -j .rela.* -j .rel* -j .rela* \
-j .reloc --target=efi-app-aarch64 refind_aa64.so refind_aa64.efi
```
Do we need native aarch64 testing or would you consider this bug resolved?
prev parent reply other threads:[~2024-03-11 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 12:34 [ISSUE] rEFInd won't cross-compile for aarch64 (glibc and musl) slymattz
2024-03-07 14:43 ` sgn
2024-03-07 14:48 ` binutils update breaks refind sgn
2024-03-07 14:51 ` sgn
2024-03-07 14:55 ` sgn
2024-03-07 14:57 ` sgn
2024-03-07 15:58 ` slymattz
2024-03-08 12:07 ` slymattz
2024-03-11 11:23 ` slymattz [this message]
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=20240311112329.255A02B739@inbox.vuxu.org \
--to=slymattz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).