mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Lucas Stach" <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] x86: efi: fix objcopy flags for barebox.efi
Date: Tue, 06 Oct 2026 08:09:52 +0000	[thread overview]
Message-ID: <1aa09454-9e09-404b-9b35-32a83f2fb151@pengutronix.de> (raw)
In-Reply-To: <2a0aae870ca1f7949fc1a9492284313be610c4cc.camel@pengutronix.de>

On 2026-10-02 12:51, Lucas Stach wrote:
> Hi Sascha,
> 
> can this patch please be added to the 2026.04 stable series? Missing
> this patch currently prevents a successful build of Barebox for the x86
> platform in Yocto wrynose.

Picked for 2026.04 stable

Sascha

> 
> Regards,
> Lucas
> 
> Am Mittwoch, dem 29.04.2026 um 10:07 +0200 schrieb
> corentin.guillevic@smile.fr:
> > From: Corentin Guillevic <corentin.guillevic@smile.fr>
> > 
> > Since the 2.46 version of binutils, a stricter target checking has been added
> > (see [1]) meaning that the --target=efi-app-x86_64 option no longer works:
> > a 'file format not recognized' error occurs.
> > 
> > Replace the --target option, which defines both the input and output targets,
> > with --output-target.
> > 
> > [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=5e83077d552ed6f81dbc092eb3ccf827a43de42c
> > 
> > Signed-off-by: Corentin Guillevic <corentin.guillevic@smile.fr>
> > ---
> >  arch/x86/Makefile | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/arch/x86/Makefile b/arch/x86/Makefile
> > index 647d075f016..9456815fa8a 100644
> > --- a/arch/x86/Makefile
> > +++ b/arch/x86/Makefile
> > @@ -62,7 +62,7 @@ KBUILD_LDFLAGS := --no-undefined
> >  
> >  OBJCOPYFLAGS_barebox.efi = \
> >  	-j .text -j .sdata -j .data -j .dynamic -j .dynsym -j .rel -j .rela \
> > -	-j .reloc -j .bbenv.* -j .bblogo.* -j .barebox_imd --target=$(TARGET)
> > +	-j .reloc -j .bbenv.* -j .bblogo.* -j .barebox_imd --output-target=$(TARGET)
> >  
> >  barebox.efi: $(KBUILD_BINARY) FORCE
> >  	$(call if_changed,objcopy)

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




      reply	other threads:[~2026-10-06  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  8:07 corentin.guillevic
2026-05-07 10:41 ` Sascha Hauer
2026-10-02 10:51 ` Lucas Stach
2026-10-06  8:09   ` Sascha Hauer [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=1aa09454-9e09-404b-9b35-32a83f2fb151@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=l.stach@pengutronix.de \
    /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