From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11756] New: package/syslinux: MBR's don't fit because of binutils new .note.gnu.property section
Date: Fri, 05 Apr 2019 06:18:31 +0000 [thread overview]
Message-ID: <bug-11756-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11756
Bug ID: 11756
Summary: package/syslinux: MBR's don't fit because of binutils
new .note.gnu.property section
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: christian at paral.in
CC: buildroot at uclibc.org
Target Milestone: ---
Corresponding bug reports:
- https://bugs.archlinux.org/task/60405
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906414
Build failure:
workspaces/qemu/host/bin/x86_64-buildroot-linux-gnu-ld -T
workspaces/qemu/build/syslinux-6.03/mbr/i386/mbr.ld -e _start -o mbr.elf mbr.o
objcopy -O binary mbr.elf mbr.bin
perl workspaces/qemu/build/syslinux-6.03/mbr/checksize.pl mbr.bin
mbr.bin: too big (452 > 440)
make[7]: *** [workspaces/qemu/build/syslinux-6.03/mbr/Makefile:42: mbr.bin]
Error 1
Description:
objcopy -O binary mbr.elf mbr.bin
perl /build/syslinux/src/syslinux/mbr/checksize.pl mbr.bin
mbr.bin: too big (452 > 440)
Fixed in Archlinux32 by stripping the .note.gnu.property in the linker scripts
of the MBRs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-04-05 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 6:18 bugzilla at busybox.net [this message]
2019-04-07 9:56 ` [Buildroot] [Bug 11756] package/syslinux: MBR's don't fit because of binutils new .note.gnu.property section bugzilla at busybox.net
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=bug-11756-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.