On 18/10/2019 14:33, Chris Adams wrote:
Once upon a time, Steve Grubb <sgrubb@xxxxxxxxxx> said:
Not sure how to proceed. I suspect this will be a bigger problem as more
people start to take advantage of the eBPF facility.
I think the issue is that you are building with clang, not gcc. gcc
defines __x86_64__ by default (on the appropriate systems of course), so
I expect the kernel headers assume it is defined. You probably would
have a number of other issues without the expected gcc macros, since
there are other conditionals that expect __x86_64__ (and potentially
other gcc macros) to exist.
Well I imagine clang will define it when targetting x86_64 output
but in this case he is targetting BPF output instead.
Adding -D__x86_64__ to the command line may be the quickest workaround
for now though.
Tom
--
Tom Hughes (tom@xxxxxxxxxx)
http://compton.nu/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
