From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 321] BPF: Errors compiling example BPF programs
Date: Mon, 15 Jul 2019 18:26:42 +0000 [thread overview]
Message-ID: <bug-321-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=321
Bug ID: 321
Summary: BPF: Errors compiling example BPF programs
Product: DPDK
Version: 19.08
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: michel@digirati.com.br
Target Milestone: ---
Created attachment 52
--> https://bugs.dpdk.org/attachment.cgi?id=52&action=edit
T1 errors
The example BPF programs t1.c, t2.c, t3.c in folder examples/bpf are no longer
compiling with the code in the repository. I've tried to compile them with
their respective commands, which are included in their headers:
$ clang -O2 -I/usr/include/aarch64-linux-gnu/ -target bpf -c t1.c 2> t1_errors
$ clang -O2 -I${RTE_SDK}/${RTE_TARGET}/include -target bpf
-Wno-int-to-void-pointer-cast -c t2.c 2> t2_errors
$ clang -O2 -I/usr/include/aarch64-linux-gnu -I${RTE_SDK}/${RTE_TARGET}/include
-target bpf -Wno-int-to-void-pointer-cast -c t3.c 2> t3_errors
I've included the suffix "2> tN_errors" to the commands above in order to
attach these error files to this issue.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-07-15 18:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-321-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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).