From: Steve Ellcey <sellcey@caviumnetworks.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: GDB build failure when using latest (ToT) GCC
Date: Mon, 27 Feb 2017 21:11:00 -0000 [thread overview]
Message-ID: <1488229905.2866.223.camel@caviumnetworks.com> (raw)
In-Reply-To: <826291c6a32e75be84c1582f7205b282@polymtl.ca>
On Mon, 2017-02-27 at 14:57 -0500, Simon Marchi wrote:
>Â
> Hi Steve,
>
> I indeed broke the build for recent GCCs in
>
> Use range-based for loop in remote_add_target_side_condition
> 8362122330c97c8c4a15da4e7ba8aa29f0c11157
>
> and fixed it right after with
>
> Remove struct keyword from range-based for loop
> d538e36decd5628c084dbd5a7de13719b8b92121
>
> I am still using an ancient 4.8 GCC, so I did not see it, but
> Sergio'sÂ
> buildbot informed me within a few minutes.  Let's just pretend it was
> aÂ
> test for the bot :).  Sorry about the inconvenience and thanks for
> beingÂ
> alert.
>
> Simon
No problem, thanks for the quick fix. Â Everything is building for me
again.
Steve Ellcey
prev parent reply other threads:[~2017-02-27 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:51 Steve Ellcey
2017-02-27 19:57 ` Simon Marchi
2017-02-27 21:11 ` Steve Ellcey [this message]
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=1488229905.2866.223.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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