From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: disable warning flags to prevent build failures
Date: Fri, 19 Aug 2016 23:06:01 +0200 [thread overview]
Message-ID: <20160819230601.144b35f9@free-electrons.com> (raw)
In-Reply-To: <1471624161-30283-1-git-send-email-vzakhar@synopsys.com>
Hello,
On Fri, 19 Aug 2016 19:29:21 +0300, Vlad Zakharov wrote:
> binutils-arc-2016.09-eng008 build fails sometimes.
>
> This happens due to the following issue:
>
> binutils configure script has CC variable that stores compiler for
> target and CC_FOR_BUILD variable that stores compiler for host.
>
> WARN_FLAGS are verified by the script to be compatible only with CC
> compiler but not with CC_FOR_BUILD compiler. Despite this WARN_FLAGS
> are passed to both CC and CC_FOR_BUILD compilers. This leads to
> unevident errors when cross-compiling. More information you can find
> in the binutils mailing list:
> https://sourceware.org/ml/binutils/2016-08/msg00117.html
>
> We are going to write a patch for bunutils that fixes the initial
> issue. Current patch contains temporary workaround. It should be
> deleted after real fix.
>
> Fixes:
> http://autobuild.buildroot.net/results/004/00455b6a8324920ad843d90ce0413451522691a8//
>
> Signed-off-by: Vlad Zakharov <vzakhar@synopsys.com>
> ---
> package/binutils/binutils.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-19 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 16:29 [Buildroot] [PATCH] binutils: disable warning flags to prevent build failures Vlad Zakharov
2016-08-19 21:06 ` Thomas Petazzoni [this message]
2016-10-03 9:38 ` Vlad Zakharov
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=20160819230601.144b35f9@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 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.