[BuildBot] News and announcements

[David Edelsohn]

On Mon, Jun 22, 2015 at 9:44 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> On Monday, June 22 2015, David Edelsohn wrote:
>
>>> 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.
>
> As you can see in the link above, the buildslave already has
> /opt/freeware/bin in the PATH, therefore everything was already covered
> in this area before.  But thanks for this.

If you have /opt/freeware/bin in your path, you do not need to use gmake.

>> 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.
>
> Right.  Strangely I wasn't seeing this problem when compiling GDB
> manually in the machine, and Peter's commit doesn't touch the m32c file.

Something increased the size of an enum (likely) or other single
debugging entry larger than 64K.

>
>> Yes, I can run the buildslave, if you want.
>
> That would be awesome!  It is currently running in my homedir at gcc111,
> but I can stop it so that you can configure the buildslave at your
> homedir if you want.  I'd prefer to keep the same name (aix-power7-1).
> I can also send you (in private) the password for the buildslave, along
> with the full command to create it.  Let me know when/what you need and
> I'll be happy to help.

I will transfer the info.

- David