Re: [BuildBot] News and announcements

[David Edelsohn <dje.gcc@gmail.com>]

On Mon, Jun 22, 2015 at 9:18 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Monday, June 22 2015, I wrote:
>
>> On Monday, June 22 2015, I wrote:
>>
>>> I will set the GDB buildslave there in a few moments, and then I'll let
>>> you know.
>>
>> Everything is set up.  Now let's wait until there's a commit to be
>> built, and check if everything is working fine.
>
> After dealing with some minor issues, I'm now seeing this:
>
>   <http://gdb-build.sergiodj.net/builders/AIX-POWER7-plain/builds/2/steps/compile%20gdb/logs/stdio>
>
> I talked to Bergner, who checked this patch in, and he said he doesn't
> know why this is happing.  I'm also not really interested (and most
> importantly, don't have the time) in maintaining the AIX builder(s), so
> if you could take a look at this I'd appreciate.
>
> As a side note, and since you are the interested part in this AIX
> buildslave, I was wondering if you want to be the responsible for it.

I restarted the buildslave with /opt/freeware/bin in your path, as we
had discussed earlier.

We saw a similar error building GCC a few months ago after the CHKP
patches.  This means that GDB now has a debug statement that is more
than 64K in length.  More recent versions of GCC allow debug
continuation lines, but this really means that m32c has a ridiculously
large enum.  It's also bloating the rest of the GDB object files, even
if DWARF can handle the length.

This error means that m32c has a real problem and AIX simply was the
canary.  Debug information that large is allowed but is evidence of a
design problem.

Yes, I can run the buildslave, if you want.

 - David