From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 75] 16.11 compile fail on RHEL 6.9
Date: Wed, 25 Jul 2018 07:51:56 +0000 [thread overview]
Message-ID: <bug-75-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=75
Bug ID: 75
Summary: 16.11 compile fail on RHEL 6.9
Product: DPDK
Version: 16.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: easetheworld@gmail.com
Target Milestone: ---
I recently updated RHEL 6.7 to 6.9 then dpdk compile failed.
== Build lib/librte_eal/linuxapp/kni
dpdk-stable-16.11.7/lib/librte_eal/linuxapp/kni/ethtool/ixgbe/kcompat.h:2837:2:
error: implicit declaration of function 'vlan_tx_tag_present'
The reason is that
vlan_tx_tag_* macros renamed to skb_vlan_tag_* in (>RHEL6.8 && <KERNEL2.6.34),
but the replacement '#define vlan_tx_tag_present skb_vlan_tag_present'
is after the use of vlan_tx_tag_present in __kc_vlan_get_protocol().
If I move the macro to the head of the file, compile succeed.
Reproducible on 16.07 as well.
I found same kcompat.h in 17.xx but it doesn't compile in RHEL 6 anyway.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-07-25 7:51 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-75-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).