From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Barak Enat <barak-7zJbC4KDGkmsTnJN9+BGXg@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Building 1.7.1 or 1.8.0-rc4 on latest CentOS 6.6 fails
Date: Thu, 18 Dec 2014 23:05:26 +0100 [thread overview]
Message-ID: <3222006.vNrEi6d4FX@xps13> (raw)
In-Reply-To: <2147099.zBhO5aAXgM@xps13>
2014-12-17 11:09, Thomas Monjalon:
> 2014-12-17 14:21, Jincheng Miao:
> > On Tue, Dec 16, 2014 at 11:12 PM, Barak Enat <barak-7zJbC4KDGkmsTnJN9+BGXg@public.gmane.org> wrote:
> > > It seems the assumption that skb_set_hash is missing in CentOS prior to
> > > version 7 is not valid anymore.
> >
> > Yes, you are right, this function skb_set_hash is added from Cent 6.6,
> > so some macro should be changed like this:
> >
> [...]
> > #if ( LINUX_VERSION_CODE < KERNEL_VERSION(3,14,0) )
> > -#if (!(RHEL_RELEASE_CODE && RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(7,0)))
> > +#if (!(RHEL_RELEASE_CODE && RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(6,6)))
> > #if (!(UBUNTU_KERNEL_CODE >= UBUNTU_KERNEL_VERSION(3,13,0,30,54) \
> > && (UBUNTU_RELEASE_CODE == UBUNTU_RELEASE_VERSION(12,4) \
> > || UBUNTU_RELEASE_CODE == UBUNTU_RELEASE_VERSION(14,4))))
>
> A patch would be appreciate :)
Should be fixed now:
http://dpdk.org/browse/dpdk/commit/?id=a8aac461cbdb
--
Thomas
prev parent reply other threads:[~2014-12-18 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 15:12 Building 1.7.1 or 1.8.0-rc4 on latest CentOS 6.6 fails Barak Enat
[not found] ` <df38f6e102cfd755dc36c575a2c75231-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-17 6:21 ` 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 [this message]
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=3222006.vNrEi6d4FX@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=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.