From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Cc: GDB <gdb@sourceware.org>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
David Edelsohn <edelsohn@us.ibm.com>,
Sanket Rathi <sanrathi@in.ibm.com>,
Nitish Mishra <nitismis@in.ibm.com>,
sergiodj@redhat.com
Subject: Re: gdb compilation failure on AIX.
Date: Tue, 13 Jun 2017 11:07:00 -0000 [thread overview]
Message-ID: <83e4dadb18ef716d2f25a922092910db@polymtl.ca> (raw)
In-Reply-To: <OF02667752.31A7EC3A-ON6525813E.003947C0-6525813E.0039C335@notes.na.collabserv.com>
On 2017-06-13 12:30, Sangamesh Mallayya wrote:
> Hi All,
>
> GDB is failing to compile on AIX.
> https://gdb-build.sergiodj.net/builders/AIX-POWER8-plain/builds/1905/steps/compile%20gdb/logs/stdio
>
> This is because of fork-inferior.o isn't being include during the final
> step of creating gdb binary.
> I guess this is mostly becuase of some of the recent change. I need to
> check the history yet.
>
> This patch should resolve this final linking issue.
>
> --- ./gdb/configure.nat_orig 2017-06-13 02:05:59.000000000 -0500
> +++ ./gdb/configure.nat 2017-06-13 02:19:41.000000000 -0500
> @@ -88,7 +88,7 @@
> # Host: IBM PowerPC running AIX aix-thread.o is not
> # listed in NATDEPFILES as it is pulled in by
> # configure.
> - NATDEPFILES='fork-child.o inf-ptrace.o rs6000-nat.o'
> + NATDEPFILES='fork-child.o inf-ptrace.o rs6000-nat.o
> fork-inferior.o'
>
> # When compiled with cc, for debugging, this argument
> # should be passed. We have no idea who our current
>
> Let me know if this is fine.
>
> Thanks,
> -Sangamesh
Hi Sangamesh,
There is already this patchset pending review, can you check if it works
for you (and reply on that thread)?
https://sourceware.org/ml/gdb-patches/2017-06/msg00250.html
CCing Sergio who did the refactoring work, he might have something to
say about it.
Simon
prev parent reply other threads:[~2017-06-13 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 10:31 Sangamesh Mallayya
2017-06-13 11:07 ` Simon Marchi [this message]
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=83e4dadb18ef716d2f25a922092910db@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=edelsohn@us.ibm.com \
--cc=gdb@sourceware.org \
--cc=nitismis@in.ibm.com \
--cc=sangamesh.swamy@in.ibm.com \
--cc=sanrathi@in.ibm.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