From: "Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] dpdk 2.1 building failure on rhel 7.2 rc1
Date: Fri, 13 Nov 2015 20:09:25 +0000 [thread overview]
Message-ID: <14a2c1418a8240ea88b0f0055cdb30f0@XCH-ALN-006.cisco.com> (raw)
Hello,
When I try to build dpdk 2.1 on rhel 7.2 rc1 I am getting following errors, appreciate if somebody could suggest a workaround of this problem. Thank you, Serguei
CC [M] /root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.o
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c: In function 'igb_ndo_bridge_getlink':
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:2289:2: error: too few arguments to function 'ndo_dflt_bridge_getlink'
return ndo_dflt_bridge_getlink(skb, pid, seq, dev, mode);
^
In file included from /usr/src/kernels/3.10.0-327.el7.x86_64/include/net/dst.h:13:0,
from /usr/src/kernels/3.10.0-327.el7.x86_64/include/net/sock.h:68,
from /usr/src/kernels/3.10.0-327.el7.x86_64/include/linux/tcp.h:23,
from /root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:34:
/usr/src/kernels/3.10.0-327.el7.x86_64/include/linux/rtnetlink.h:87:12: note: declared here
extern int ndo_dflt_bridge_getlink(struct sk_buff *skb, u32 pid, u32 seq,
^
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c: In function 'igb_xmit_frame_ring':
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:5503:2: error: implicit declaration of function 'vlan_tx_tag_present' [-Werror=implicit-function-declaration]
if (vlan_tx_tag_present(skb)) {
^
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:5505:3: error: implicit declaration of function 'vlan_tx_tag_get' [-Werror=implicit-function-declaration]
tx_flags |= (vlan_tx_tag_get(skb) << IGB_TX_FLAGS_VLAN_SHIFT);
^
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c: In function 'igb_ndo_get_vf_config':
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:9472:5: error: 'struct ifla_vf_info' has no member named 'tx_rate'
ivi->tx_rate = adapter->vf_data[vf].tx_rate;
^
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c: In function 'igb_ndo_bridge_getlink':
/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:2291:1: error: control reaches end of non-void function [-Werror=return-type]
}
^
cc1: all warnings being treated as errors
make[10]: *** [/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.o] Error 1
make[9]: *** [_module_/root/dpdk/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni] Error 2
make[8]: *** [sub-make] Error 2
make[7]: *** [rte_kni.ko] Error 2
make[6]: *** [kni] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [x86_64-native-linuxapp-gcc_install] Error 2
make: *** [install] Error 2
next reply other threads:[~2015-11-13 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 20:09 Serguei Bezverkhi (sbezverk) [this message]
2015-12-03 18:31 Roberts, Lee A.
2015-12-03 19:06 ` Thomas Monjalon
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=14a2c1418a8240ea88b0f0055cdb30f0@XCH-ALN-006.cisco.com \
--to=sbezverk@cisco.com \
--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).