From: Peter Maydell <peter.maydell@linaro.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] ppc: Include asm/ptrace.h for pt_regs struct definition
Date: Mon, 14 Mar 2022 17:05:03 +0000 [thread overview]
Message-ID: <CAFEAcA_SCwN3LpdADuYs7gTqgravOqDan-D6BrcAW_tb0omP8g@mail.gmail.com> (raw)
In-Reply-To: <20220314170223.554679-1-raj.khem@gmail.com>
On Mon, 14 Mar 2022 at 17:02, Khem Raj <raj.khem@gmail.com> wrote:
>
> Fixes
> ../qemu-6.2.0/linux-user/host/ppc64/../ppc/host-signal.h:16:32: error: incomplete definition of type 'struct pt_regs'
> return uc->uc_mcontext.regs->nip;
> ~~~~~~~~~~~~~~~~~~~~^
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Cc: Richard Henderson <richard.henderson@linaro.org>
> ---
> linux-user/include/host/ppc/host-signal.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/linux-user/include/host/ppc/host-signal.h b/linux-user/include/host/ppc/host-signal.h
> index b80384d135..43ee2eee3b 100644
> --- a/linux-user/include/host/ppc/host-signal.h
> +++ b/linux-user/include/host/ppc/host-signal.h
> @@ -11,6 +11,10 @@
> #ifndef PPC_HOST_SIGNAL_H
> #define PPC_HOST_SIGNAL_H
>
> +#if defined(__powerpc__)
Why is this #if defined() needed ?
> +#include <asm/ptrace.h>
> +#endif
What host distro are you building with? We do test ppc64be at least
in our CI, and that builds OK.
thanks
-- PMM
next prev parent reply other threads:[~2022-03-14 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 17:02 [PATCH] ppc: Include asm/ptrace.h for pt_regs struct definition Khem Raj
2022-03-14 17:05 ` Peter Maydell [this message]
2022-03-14 17:22 ` Khem Raj
2022-03-14 18:06 ` Peter Maydell
2022-03-14 18:52 ` Richard Henderson
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=CAFEAcA_SCwN3LpdADuYs7gTqgravOqDan-D6BrcAW_tb0omP8g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=raj.khem@gmail.com \
--cc=richard.henderson@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).