From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boot/syslinux: fix build with binutils note gnu property section
Date: Sun, 07 Apr 2019 11:54:45 +0200 [thread overview]
Message-ID: <87ftqujg2i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190405064055.19030-1-christian@paral.in> (Christian Stewart's message of "Thu, 4 Apr 2019 23:40:55 -0700")
>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
> This fixes the following build error with newer binutils:
> objcopy -O binary mbr.elf mbr.bin
> perl /build/syslinux/src/syslinux/mbr/checksize.pl mbr.bin
> mbr.bin: too big (452 > 440)
> Corresponding bug reports:
> - https://bugs.archlinux.org/task/60405
> - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906414
> Strips the .note.gnu.property in the linker scripts for the MBRs.
> Signed-off-by: Christian Stewart <christian@paral.in>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-04-07 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 6:40 [Buildroot] [PATCH 1/1] boot/syslinux: fix build with binutils note gnu property section Christian Stewart
2019-04-07 8:55 ` Yann E. MORIN
2019-04-07 9:54 ` Peter Korsgaard [this message]
2019-04-14 20:28 ` Peter Korsgaard
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=87ftqujg2i.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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