From: Barak Enat <barak-7zJbC4KDGkmsTnJN9+BGXg@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Building 1.7.1 or 1.8.0-rc4 on latest CentOS 6.6 fails
Date: Tue, 16 Dec 2014 17:12:58 +0200 [thread overview]
Message-ID: <df38f6e102cfd755dc36c575a2c75231@mail.gmail.com> (raw)
Hi
When building 1.7.1 or 1.8.0-rc4 on recent CentOS 6 (6.6) I got this error:
In file included from
/home/makerpm/rpmbuild/BUILD/dpdk-1.8.0/lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_osdep.h:41,
from
/home/makerpm/rpmbuild/BUILD/dpdk-1.8.0/lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_hw.h:31,
from
/home/makerpm/rpmbuild/BUILD/dpdk-1.8.0/lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_api.h:31,
from
/home/makerpm/rpmbuild/BUILD/dpdk-1.8.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/e1000_82575.c:38:
/home/makerpm/rpmbuild/BUILD/dpdk-1.8.0/lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h:3870:
error: conflicting types for 'skb_set_hash'
include/linux/skbuff.h:620: note: previous definition of 'skb_set_hash' was
here
make[8]: ***
[/home/makerpm/rpmbuild/BUILD/dpdk-1.8.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/e1000_82575.o]
Error 1
It seems the assumption that skb_set_hash is missing in CentOS prior to
version 7 is not valid anymore.
Didn't see a fix of it in trunk or in the patches.
Thanks,
Barak
next reply other threads:[~2014-12-16 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 15:12 Barak Enat [this message]
[not found] ` <df38f6e102cfd755dc36c575a2c75231-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-17 6:21 ` Building 1.7.1 or 1.8.0-rc4 on latest CentOS 6.6 fails Jincheng Miao
[not found] ` <CAF-jSjRe4tT-t_iVAJWdmMFnF5K2Ls6LhydUPsgNQj0bWfUBdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-17 10:09 ` Thomas Monjalon
2014-12-18 22:05 ` 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=df38f6e102cfd755dc36c575a2c75231@mail.gmail.com \
--to=barak-7zjbc4kdgkmstnjn9+bgxg@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.