mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jonas Bonn <jonas@southpole.se>,
	 Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Stafford Horne <shorne@gmail.com>,
	 linux-openrisc@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] usr/include: openrisc: don't HDRTEST bpf_perf_event.h
Date: Sun, 4 May 2025 08:31:50 +0900	[thread overview]
Message-ID: <CAK7LNAQr9Ceb36R44Kqvn6bj5qAB3BxSW5-RKXaaejoAQEubPA@mail.gmail.com> (raw)
In-Reply-To: <21182762-30b9-49e5-aa6c-a0f967d81529@infradead.org>

On Sun, May 4, 2025 at 8:23 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
>
>
> On 5/3/25 9:13 AM, Masahiro Yamada wrote:
> > On Sun, May 4, 2025 at 1:01 AM Masahiro Yamada <masahiroy@kernel.org> wrote:
> >>
> >> On Sat, Apr 26, 2025 at 12:08 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> >>>
> >>> Since openrisc does not support PERF_EVENTS, omit the HDRTEST of
> >>> bpf_perf_event.h for arch/openrisc/.
> >>>
> >>> Fixes a build error:
> >>> usr/include/linux/bpf_perf_event.h:14:28: error: field 'regs' has incomplete type
> >>
> >>
> >>
> >> Where can I get openrisc compiler that enables CONFIG_CC_CAN_LINK?
> >
> > Never mind.
> > I downloaded a one from
> > https://github.com/stffrdhrn/or1k-toolchain-build/releases
> >
> > Hmm, I did not observe an error like that.
> >
> > Instead, I got a different error message.
> >
> >   HDRTEST usr/include/linux/bpf_perf_event.h
> > In file included from <command-line>:
> > ./usr/include/linux/bpf_perf_event.h:15:9: error: unknown type name '__u64'
> >    15 |         __u64 sample_period;
> >       |         ^~~~~
> > ./usr/include/linux/bpf_perf_event.h:16:9: error: unknown type name '__u64'
> >    16 |         __u64 addr;
> >       |         ^~~~~
> >
>
> Does HDRTEST use the #include files from the header that is being tested?
>
> usr/include/linux/bpf_perf_event.h #includes <asm/bpf_perf_event.h>
> (from usr/include/ ??) which #includes <asm-generic/bpf_perf_event.h>
> (from usr/include/ ??) which #includes <linux/ptrace.h> (from usr/include/ ??)
> which #includes <linux/types.h>.  I don't see this problem in my builds.
>
> I do still continue to see this failure:
>
>   HDRTEST usr/include/linux/bpf_perf_event.h
> In file included from <command-line>:
> ./usr/include/linux/bpf_perf_event.h:14:28: error: field 'regs' has incomplete type
>    14 |         bpf_user_pt_regs_t regs;
>       |                            ^~~~
> make[5]: *** [../usr/include/Makefile:85: usr/include/linux/bpf_perf_event.hdrtest] Error 1


Sorry, my local issue.

Applied now.



-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2025-05-03 23:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26  3:08 Randy Dunlap
2025-04-26  6:00 ` Stafford Horne
2025-04-26 15:45   ` Randy Dunlap
2025-04-26 16:14     ` Stafford Horne
2025-05-03 16:01 ` Masahiro Yamada
2025-05-03 16:13   ` Masahiro Yamada
2025-05-03 23:23     ` Randy Dunlap
2025-05-03 23:31       ` Masahiro Yamada [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=CAK7LNAQr9Ceb36R44Kqvn6bj5qAB3BxSW5-RKXaaejoAQEubPA@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --cc=jonas@southpole.se \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-openrisc@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /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

all inboxes | Powered by JetHome®