Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Wilson <jim.wilson@linaro.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
	Yao Qi <qiyaoltc@gmail.com>, 	Pedro Alves <palves@redhat.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: build bot failure
Date: Sat, 11 Jun 2016 17:00:00 -0000	[thread overview]
Message-ID: <CABXYE2WgQ7s8Tz=aJpjkTm-LvAKLkoxi1F+AzVRxsmeQhMUsjg@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnyntu9hCgse3PROdfO1OD61C98Jy9JSuJMH1b4BmpFpdQg@mail.gmail.com>

On Sat, Jun 11, 2016 at 5:26 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
> The AIX system has not changed, so some change to GDB broke the build
> on AIX.  It's warning about missing declarations. Is this related to
> the C++ change?

An aarch64 binutils patch from me broke it.  I can't see anything
wrong with my patch.  I can't tell why AIX builds are broken without
access to an AIX system, and my request for a compile farm account 2.5
weeks ago hasn't gotten a response yet, so I'm stuck.

https://sourceware.org/ml/binutils/2016-05/msg00103.html
https://sourceware.org/ml/gdb-testers/2016-q2/msg03281.html

Jim


  reply	other threads:[~2016-06-11 17:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  0:40 Jim Wilson
2016-05-24  8:26 ` Yao Qi
2016-05-24 10:39   ` Yao Qi
2016-05-24 16:30     ` Jim Wilson
2016-05-24 16:48     ` Pedro Alves
2016-05-25  8:07       ` Yao Qi
2016-06-10 16:27         ` Jim Wilson
2016-06-10 18:47           ` Sergio Durigan Junior
2016-06-11 12:26             ` David Edelsohn
2016-06-11 17:00               ` Jim Wilson [this message]
2016-06-12 17:27                 ` David Edelsohn
2016-06-22 23:15                   ` Jim Wilson
2016-06-23  0:57                     ` Sergio Durigan Junior
2016-11-14 11:06                   ` Yao Qi
2016-11-14 13:01                     ` David Edelsohn

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='CABXYE2WgQ7s8Tz=aJpjkTm-LvAKLkoxi1F+AzVRxsmeQhMUsjg@mail.gmail.com' \
    --to=jim.wilson@linaro.org \
    --cc=dje.gcc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.com \
    --cc=sergiodj@redhat.com \
    /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