From: Jim Wilson <jim.wilson@linaro.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Yao Qi <qiyaoltc@gmail.com>, Pedro Alves <palves@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: build bot failure
Date: Wed, 22 Jun 2016 23:15:00 -0000 [thread overview]
Message-ID: <CABXYE2V1GxOtEMimg5P7ih-r-NLDrvq33=eyiYUrhZZXTFQvag@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnykERyKGrF4uaU+o52TOTHoKv0Vfqnp+c9D4mW+Bq8MVew@mail.gmail.com>
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.
I tried a build of gcc-5.x using the existing gcc-4.8.4 release, and
ran into problem with shared libraries. For some reason, the
installed gcc insists on using libraries in the build tree instead of
libraries from the install tree, and then fails with a linker error.
This is apparently an AIX feature, and I don't know how to work around
it. I also tried builds with xlc, and discovered that neither
binutils nor gcc builds with xlc out of the box. Apparently no one is
testing this.
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.
We could maybe request a new gcc install on the gcc111 AIX machine,
but I don't know if this will accomplish anything useful anytime soon.
Jim
next prev parent reply other threads:[~2016-06-22 23:15 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 [this message]
2016-06-23 0:57 ` Sergio Durigan Junior
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='CABXYE2V1GxOtEMimg5P7ih-r-NLDrvq33=eyiYUrhZZXTFQvag@mail.gmail.com' \
--to=jim.wilson@linaro.org \
--cc=dje.gcc@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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