From: Alan Hayward <Alan.Hayward@arm.com>
To: Simon Marchi <simark@simark.ca>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [OBV][PATCH] Fix Arm build
Date: Tue, 26 Mar 2019 17:14:00 -0000 [thread overview]
Message-ID: <571D8947-F0EF-4BD9-8CC8-EF89AE507467@arm.com> (raw)
In-Reply-To: <471bd2e4-3bbe-8e43-b2eb-0561437f7d33@simark.ca>
> On 26 Mar 2019, at 17:03, Simon Marchi <simark@simark.ca> wrote:
>
> On 2019-03-26 7:43 a.m., Alan Hayward wrote:
>> [Should have checked this when I fixed s390 build.
>> Going to see about getting an Arm box into buildbot - booting Linux
>> in Qemu-AArch64 in AArch32 mode on a AArch64 box might be fast enough to
>> use as an Arm machine]
>>
>>
>> Add missing include.
>>
>> 2019-03-26 Alan Hayward <alan.hayward@arm.com>
>>
>> * arm-linux-nat.c: Add include.
>> ---
>> gdb/arm-linux-nat.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/gdb/arm-linux-nat.c b/gdb/arm-linux-nat.c
>> index b54bd5afe9..52668da9fc 100644
>> --- a/gdb/arm-linux-nat.c
>> +++ b/gdb/arm-linux-nat.c
>> @@ -38,6 +38,7 @@
>> #include <sys/procfs.h>
>>
>> #include "nat/linux-ptrace.h"
>> +#include "linux-tdep.h"
>>
>> /* Prototypes for supply_gregset etc. */
>> #include "gregset.h"
>>
>
>
> powerpc seems to have this problem as well :)
>
> /home/smarchi/src/binutils-gdb/gdb/ppc-linux-nat.c:2616:22: error: ‘linux_get_hwcap2’ was not declared in this scope
>
> Simon
Will fix this too.... :(
Alan.
prev parent reply other threads:[~2019-03-26 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 11:43 Alan Hayward
2019-03-26 17:03 ` Simon Marchi
2019-03-26 17:14 ` Alan Hayward [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=571D8947-F0EF-4BD9-8CC8-EF89AE507467@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=simark@simark.ca \
/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