From: Sameeh Jubran <sameeh@daynix.com>
To: dev@dpdk.org, Ophir Munk <ophirmu@mellanox.com>
Cc: Yan Vugenfirer <yan@daynix.com>
Subject: Re: [dpdk-dev] Compiling RSS ebpf
Date: Fri, 25 May 2018 11:53:34 +0300 [thread overview]
Message-ID: <CAKPgXcHo+FuFMFrQhgzfg+D0xNpb-6TepaVsdXMGMSzdppJfsg@mail.gmail.com> (raw)
In-Reply-To: <CAKPgXcG-bCr1PuOsCPscjgpgg5gtU1uKt6e0aFYCGFXtcmN+sQ@mail.gmail.com>
Ping.
On Sun, May 13, 2018 at 1:16 PM, Sameeh Jubran <sameeh@daynix.com> wrote:
> Sorry I have accidentally sent my last email without finishing it.
>
> I believe it is due misconfiguration of the linux headers and their
> inclusion. Anyone else faced these errors?
>
>
> On Sun, May 13, 2018 at 1:10 PM, Sameeh Jubran <sameeh@daynix.com> wrote:
>
>> Hi All,
>>
>> I am attempting to compile the rss epbf program dpdk and I am getting too
>> much compilation errors, is there anything specific that I need to
>> configure when compiling?
>>
>> I am running the following line:
>>
>> clang -O2 -emit-llvm -c tap_bpf_program.c -o - | llc -march=bpf
>> -filetype=obj -o tap_bpf_program.o
>>
>> I think it is due to some misconfiguration of
>>
> The errors I am getting:
>>
>> tap_bpf_program.c:157:37: warning: implicit declaration of function
>> 'offsetof' is invalid in C99 [-Wimplicit-function-declaration]
>> __u8 *src_dst_addr = data + off + offsetof(struct iphdr,
>> saddr);
>> ^
>> tap_bpf_program.c:157:46: error: expected expression
>> __u8 *src_dst_addr = data + off + offsetof(struct iphdr,
>> saddr);
>> ^
>> tap_bpf_program.c:157:60: error: use of undeclared identifier 'saddr'
>> __u8 *src_dst_addr = data + off + offsetof(struct iphdr,
>> saddr);
>> ^
>> tap_bpf_program.c:180:11: error: use of undeclared identifier 'TC_ACT_OK'
>> return TC_ACT_OK;
>> ^
>> tap_bpf_program.c:182:15: error: expected expression
>> offsetof(struct ipv6hdr, saddr);
>> ^
>> tap_bpf_program.c:182:31: error: use of undeclared identifier 'saddr'
>> offsetof(struct ipv6hdr, saddr);
>> ^
>> tap_bpf_program.c:204:10: error: use of undeclared identifier
>> 'TC_ACT_PIPE'
>> return TC_ACT_PIPE;
>> ^
>> tap_bpf_program.c:212:9: error: use of undeclared identifier
>> 'TC_ACT_RECLASSIFY'
>> return TC_ACT_RECLASSIFY;
>> ^
>> tap_bpf_program.c:222:1: error: expected parameter declarator
>> RSS(l3_l4)
>> ^
>> tap_bpf_program.c:216:12: note: expanded from macro 'RSS'
>> __section(#L) int \
>> ^
>> <scratch space>:76:1: note: expanded from here
>> "l3_l4"
>> ^
>> tap_bpf_program.c:222:1: error: expected ')'
>> tap_bpf_program.c:216:12: note: expanded from macro 'RSS'
>> __section(#L) int \
>> ^
>> <scratch space>:76:1: note: expanded from here
>> "l3_l4"
>> ^
>> tap_bpf_program.c:222:1: note: to match this '('
>> tap_bpf_program.c:216:11: note: expanded from macro 'RSS'
>> __section(#L) int \
>> ^
>> tap_bpf_program.c:222:1: warning: type specifier missing, defaults to
>> 'int' [-Wimplicit-int]
>> RSS(l3_l4)
>> ^
>> tap_bpf_program.c:216:2: note: expanded from macro 'RSS'
>> __section(#L) int \
>> ^
>> tap_bpf_program.c:222:1: error: expected ';' after top level declarator
>> tap_bpf_program.c:216:16: note: expanded from macro 'RSS'
>> __section(#L) int \
>> ^
>> fatal error: too many errors emitted, stopping now [-ferror-limit=]
>> 6 warnings and 20 errors generated.
>> sameeh@bark:~/Builds/bpf_rss/dpdk/drivers/net/tap$ clear
>>
>> --
>> Respectfully,
>> *Sameeh Jubran*
>> *Linkedin <https://il.linkedin.com/pub/sameeh-jubran/87/747/a8a>*
>> *Software Engineer @ Daynix <http://www.daynix.com>.*
>>
>
>
>
> --
> Respectfully,
> *Sameeh Jubran*
> *Linkedin <https://il.linkedin.com/pub/sameeh-jubran/87/747/a8a>*
> *Software Engineer @ Daynix <http://www.daynix.com>.*
>
--
Respectfully,
*Sameeh Jubran*
*Linkedin <https://il.linkedin.com/pub/sameeh-jubran/87/747/a8a>*
*Software Engineer @ Daynix <http://www.daynix.com>.*
next prev parent reply other threads:[~2018-05-25 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 10:10 Sameeh Jubran
2018-05-13 10:16 ` Sameeh Jubran
2018-05-25 8:53 ` Sameeh Jubran [this message]
2018-05-29 15:48 ` Ophir Munk
2018-06-06 12:06 ` Sameeh Jubran
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=CAKPgXcHo+FuFMFrQhgzfg+D0xNpb-6TepaVsdXMGMSzdppJfsg@mail.gmail.com \
--to=sameeh@daynix.com \
--cc=dev@dpdk.org \
--cc=ophirmu@mellanox.com \
--cc=yan@daynix.com \
/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).