From: slymattz <slymattz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: binutils update breaks refind
Date: Fri, 08 Mar 2024 13:07:49 +0100 [thread overview]
Message-ID: <20240308120749.4B596222FA@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: 951 bytes --]
New comment by slymattz on void-packages repository
https://github.com/void-linux/void-packages/issues/49170#issuecomment-1985581788
Comment:
> ```diff
> Index: refind-0.14.0.2/Make.common
> ===================================================================
> --- refind-0.14.0.2.orig/Make.common
> +++ refind-0.14.0.2/Make.common
> @@ -140,8 +140,6 @@ endif
>
> ifeq ($(ARCH), aarch64)
> GNUEFI_CFLAGS += -DEFIAARCH64
> - FORMAT = -O binary
> - FORMAT_DRIVER = -O binary
> SUBSYSTEM_LDFLAG = -defsym=EFI_SUBSYSTEM=0xa
> LDFLAGS += --warn-common --no-undefined --fatal-warnings
>
> ```
>
> Built, not tested in anyway
Just wanted to confirm that removing these two lines also enables refind to build successfully for aarch64-glibc and aarch64-musl.
BTW, let me post a link to your patch upstream, just for the record:
https://sourceforge.net/p/refind/discussion/general/thread/3ca1db9256/
next prev parent reply other threads:[~2024-03-08 12:07 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 [this message]
2024-03-11 11:23 ` slymattz
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=20240308120749.4B596222FA@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).