On Sun, May 4, 2025 at 8:23 AM Randy Dunlap <rdun...@infradead.org> wrote:
>
>
>
> On 5/3/25 9:13 AM, Masahiro Yamada wrote:
> > On Sun, May 4, 2025 at 1:01 AM Masahiro Yamada <masahi...@kernel.org> wrote:
> >>
> >> On Sat, Apr 26, 2025 at 12:08 PM Randy Dunlap <rdun...@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 via email to