Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] boot/syslinux: disable syslinux legacy-BIOS for toolchains affected by binutils bug 19615
Date: Wed, 19 Jul 2017 14:52:46 +0200	[thread overview]
Message-ID: <87tw28bnc1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170704120110.29107-2-romain.naour@smile.fr> (Romain Naour's message of "Tue, 4 Jul 2017 14:01:10 +0200")

>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:

 > Since [1] syslinux is build with the target toolchain in order to
 > properly build with gnu-efi package.
 > But toolchains built with binutils 2.26 break the syslinux legacy-BIOS
 > build as reported [2].

 > Thanks to Beno?t Allard for the investigation and the link to the
 > binutils bug [3].

 > [1] 6e432d5ecb46959f3c27dbbca48e41512bb40a70
 > [2] http://lists.busybox.net/pipermail/buildroot/2017-July/196253.html
 > [3] https://sourceware.org/bugzilla/show_bug.cgi?id=19615

 > Signed-off-by: Romain Naour <romain.naour@smile.fr>
 > Cc: Beno?t Allard <benoit.allard@greenbone.net>

Committed to 2017.05.x, thanks.

I take it that our internal 2.26.1 binutils isn't affected by this?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-07-19 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 12:01 [Buildroot] [PATCH 1/2] toolchain: CodeSourcery AMD64 affected by PR19615 Romain Naour
2017-07-04 12:01 ` [Buildroot] [PATCH 2/2] boot/syslinux: disable syslinux legacy-BIOS for toolchains affected by binutils bug 19615 Romain Naour
2017-07-19 12:52   ` Peter Korsgaard [this message]
2017-07-04 16:32 ` [Buildroot] [PATCH 1/2] toolchain: CodeSourcery AMD64 affected by PR19615 Thomas Petazzoni
2017-07-19 12:49 ` 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=87tw28bnc1.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