public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org,
	James Hilliard <james.hilliard1@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH/next v2 2/2] package/fwupd-efi: bump version to 1.8
Date: Sat, 28 Mar 2026 19:23:29 +0100	[thread overview]
Message-ID: <36ceeca8584fb05d82c7106f75be2f7e@free.fr> (raw)
In-Reply-To: <20260302210037.1931571-2-bernd@kuhls.net>

On 02/03/2026 22:00, Bernd Kuhls wrote:
> https://github.com/fwupd/fwupd-efi/releases/tag/1.8
> 
> Added TARGET_LD to _MESON_EXTRA_BINARIES due to upstream commit
> https://github.com/fwupd/fwupd-efi/commit/a7ac71e3b391e040d9ca0d58d2d186be5b60b631
> which causes a misdetection of the linker used.
> 
> Build log without specifying TARGET_LD:
> 
>   Program ld.bfd found: YES (/usr/bin/ld.bfd)
>   [...]
>   /usr/bin/ld.bfd: cannot represent machine `aarch64'
> 
> Build log with specifying TARGET_LD:
> 
>   Program ld.bfd found: YES
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-03-28 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 21:00 [Buildroot] [PATCH/next 1/2] package/gnu-efi: bump version to 4.0.4 Bernd Kuhls
2026-03-02 21:00 ` [Buildroot] [PATCH/next v2 2/2] package/fwupd-efi: bump version to 1.8 Bernd Kuhls
2026-03-28 18:23   ` Julien Olivain via buildroot [this message]
2026-03-28 18:16 ` [Buildroot] [PATCH/next 1/2] package/gnu-efi: bump version to 4.0.4 Julien Olivain via buildroot

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=36ceeca8584fb05d82c7106f75be2f7e@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.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