From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package, toolchain: remove BR2_TOOLCHAIN_HAS_GCC_BUG_* options
Date: Sat, 30 Jan 2016 08:55:33 +0100 [thread overview]
Message-ID: <56AC6C75.7010103@mind.be> (raw)
In-Reply-To: <1454109890-19470-1-git-send-email-thomas.petazzoni@free-electrons.com>
On 30-01-16 00:24, Thomas Petazzoni wrote:
> Quite some time ago, we added the options
> BR2_TOOLCHAIN_HAS_GCC_BUG_58595 and BR2_TOOLCHAIN_HAS_GCC_BUG_58854 to
> indicate if the toolchain was affected by those gcc bugs, which were
> causing build failure with a number of packages.
>
> With the recent change in the external toolchain logic to provide only
> the latest version of each toolchain "family", all the toolchains
> which were affected by those issues disappeared from Buildroot. Those
> options are no longer being selected anywhere, and being blind
> options, it means their value is always going to be "disabled".
>
> Conquently, this commit removes those options completely, and updates
> all the packages where they were used.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-01-30 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 23:24 [Buildroot] [PATCH] package, toolchain: remove BR2_TOOLCHAIN_HAS_GCC_BUG_* options Thomas Petazzoni
2016-01-30 7:55 ` Arnout Vandecappelle [this message]
2016-01-30 10:03 ` 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=56AC6C75.7010103@mind.be \
--to=arnout@mind.be \
--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.