From: David Edelsohn <dje.gcc@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Doug Evans <dje@google.com>, "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [BuildBot] News and announcements
Date: Tue, 23 Jun 2015 01:51:00 -0000 [thread overview]
Message-ID: <CAGWvnym8dLqRxz9WHBbAQnvZm2wdvqUV4oNvL-CHzs7VJ_Xb+A@mail.gmail.com> (raw)
In-Reply-To: <87y4jbi4fw.fsf@redhat.com>
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
next prev parent reply other threads:[~2015-06-23 1:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 7:02 David Edelsohn
2015-06-21 22:56 ` David Edelsohn
2015-06-22 19:05 ` Sergio Durigan Junior
2015-06-22 19:50 ` Sergio Durigan Junior
2015-06-23 1:18 ` Sergio Durigan Junior
2015-06-23 1:32 ` David Edelsohn
2015-06-23 1:44 ` Sergio Durigan Junior
2015-06-23 1:51 ` David Edelsohn [this message]
2015-06-23 2:11 ` Sergio Durigan Junior
2015-06-23 2:13 ` David Edelsohn
2015-06-23 2:26 ` Sergio Durigan Junior
2015-06-23 4:20 ` David Edelsohn
2015-06-23 4:37 ` David Edelsohn
2015-06-23 20:11 ` Sergio Durigan Junior
[not found] <87616mmcks.fsf@sergiodj.net>
2015-06-17 20:37 ` Simon Marchi
2015-06-17 21:58 ` Sergio Durigan Junior
2015-06-17 22:10 ` Doug Evans
2015-06-19 19:01 ` Sergio Durigan Junior
[not found] ` <86fv5orqd0.fsf@gmail.com>
2015-06-19 19:05 ` Sergio Durigan Junior
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=CAGWvnym8dLqRxz9WHBbAQnvZm2wdvqUV4oNvL-CHzs7VJ_Xb+A@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--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