From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11861] New: Syslinux EFI binaries are broken on 2019.05-rc1 (binutils >= 2.31)
Date: Fri, 10 May 2019 07:41:34 +0000 [thread overview]
Message-ID: <bug-11861-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11861
Bug ID: 11861
Summary: Syslinux EFI binaries are broken on 2019.05-rc1
(binutils >= 2.31)
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: sam at gpsm.co.uk
CC: buildroot at uclibc.org
Target Milestone: ---
Binutils >= 2.31 writes two PT_LOAD segements by default. This
is not supported by the wrapper.c script used to convert the shared
object into an elf binary.
Refs:
https://wiki.syslinux.org/wiki/index.php?title=Building
https://www.syslinux.org/archives/2018-August/026167.html
https://salsa.debian.org/images-team/syslinux/commit/012e1dd312eb8c1f9a52239966e0be0169d7af98
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-05-10 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 7:41 bugzilla at busybox.net [this message]
2023-12-23 18:49 ` [Buildroot] [Bug 11861] Syslinux EFI binaries are broken on 2019.05-rc1 (binutils >= 2.31) bugzilla
2024-06-15 14:49 ` bugzilla
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-11861-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox