From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc 4.8.3: add patch for PR60155
Date: Wed, 2 Jul 2014 16:18:26 +0200 [thread overview]
Message-ID: <20140702161826.76ea2d0c@free-electrons.com> (raw)
In-Reply-To: <1404308617-5370-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 2 Jul 2014 10:43:37 -0300, Gustavo Zacarias wrote:
> Fixes:
> http://autobuild.buildroot.net/results/6c8/6c8c3cb19a6f98f6f27986b671d48ee092fdf7cc/
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/gcc/4.8.3/842-PR60155.patch | 111 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 111 insertions(+)
> create mode 100644 package/gcc/4.8.3/842-PR60155.patch
>
> diff --git a/package/gcc/4.8.3/842-PR60155.patch b/package/gcc/4.8.3/842-PR60155.patch
> new file mode 100644
> index 0000000..7bc2122
> --- /dev/null
> +++ b/package/gcc/4.8.3/842-PR60155.patch
> @@ -0,0 +1,111 @@
> +From gcc bugzilla https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60155
> +Upstream status: in trunk.
Just to confirm: is it 4.9.0 already?
Also, it doesn't immediately fix the autobuild issue, because the
autobuild issue occurs with a pre-built Crosstool-NG toolchain. I'll
temporarily add an exception in the autobuilders, and then hopefully
Yann will pick up the patch in Crosstool-NG and at some point we'll be
able to update the pre-built Crosstool-NG toolchain.
Thanks a lot for the investigation!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-02 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 13:43 [Buildroot] [PATCH] gcc 4.8.3: add patch for PR60155 Gustavo Zacarias
2014-07-02 14:18 ` Thomas Petazzoni [this message]
2014-07-02 14:23 ` Gustavo Zacarias
2014-07-02 14:35 ` Thomas Petazzoni
2014-07-02 15:14 ` 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=20140702161826.76ea2d0c@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.