From: Yao Qi <qiyaoltc@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Jim Wilson <jim.wilson@linaro.org>,
Sergio Durigan Junior <sergiodj@redhat.com>,
Pedro Alves <palves@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: build bot failure
Date: Mon, 14 Nov 2016 11:06:00 -0000 [thread overview]
Message-ID: <CAH=s-PMHZM66_CcM2f1XEzwnqY4b393uJc25cgrHgaLbbLMeQA@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnykERyKGrF4uaU+o52TOTHoKv0Vfqnp+c9D4mW+Bq8MVew@mail.gmail.com>
On Sun, Jun 12, 2016 at 6:27 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> Jim,
>
> The problem is the debug stabstring for bfd_reloc_code_real_names now
> overflows the maximum length. Your patch overflowed the limit.
>
> More recent releases of GCC for AIX added support for stab
> continuation strings, but not the release installed on the machine
> running the buildbot.
>
Hi David,
I am still unable to build GDB on AIX (gcc111) due to this gcc/ld issue
today. I know you've already started to address this issue (we talked
about this in Cauldron in July). When can we get a new toolchain
installed on it or get it replaced by a new one?
I touch some rs6000 aix software single step code, and I'd like to test
GDB on aix to make sure my patches regression-free on aix.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-11-14 11:06 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
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 [this message]
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='CAH=s-PMHZM66_CcM2f1XEzwnqY4b393uJc25cgrHgaLbbLMeQA@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gdb@sourceware.org \
--cc=jim.wilson@linaro.org \
--cc=palves@redhat.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