From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jim Wilson <jim.wilson@linaro.org>
Cc: David Edelsohn <dje.gcc@gmail.com>, Yao Qi <qiyaoltc@gmail.com>,
Pedro Alves <palves@redhat.com>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: build bot failure
Date: Thu, 23 Jun 2016 00:57:00 -0000 [thread overview]
Message-ID: <87y45wracv.fsf@redhat.com> (raw)
In-Reply-To: <CABXYE2V1GxOtEMimg5P7ih-r-NLDrvq33=eyiYUrhZZXTFQvag@mail.gmail.com> (Jim Wilson's message of "Wed, 22 Jun 2016 16:15:03 -0700")
On Wednesday, June 22 2016, Jim Wilson wrote:
> On Sun, Jun 12, 2016 at 10:27 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
>> 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.
>
> I finally got my compile farm account over the weekend, and have
> confirmed what David Edelsohn already said. bimutils/gdb will build
> without debug info, but with debug info the build fails because of a
> bug in the gcc-4.8.1 release in /opt/freeware/bin. This bug is fixed
> in gcc-5.x.
Thanks for looking into this, Jim.
> Since there is no problem with my patch, and since I don't have any
> business or personal interest in AIX, I'm not planning to look into
> this any further.
Right. This goes in the same direction as I am heading: reduce the
noise caused by some targets on our BuildBot.
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2016-06-23 0:57 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 [this message]
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=87y45wracv.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gdb@sourceware.org \
--cc=jim.wilson@linaro.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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