DPDK patches and discussions
 help / color / mirror / Atom feed

From: <martin_curran-gray@keysight.com>
To: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: fix build with backported kernel
Date: Wed, 2 Nov 2016 16:19:48 +0000	[thread overview]
Message-ID: <22C95CA62CBADB498D32A348F0F073BC269617BF@wcosexch02k.cos.is.keysight.com> (raw)

Hi ,

Sorry, struggling to see what happened to this thread

I managed to get dpdk 2.2.0 to build on CentOs 6.8 by sorting the MSIX_ENTRY_CTRL_MASKBIT

But I'm trying to get 16.7 to run on 6.8, and am hitting the   vlan_tx_tag_present(_skb)

I tried just putting a bare
#define  vlan_tx_tag_present(_skb) 0
line in the two kcompat.h files
one for igb and one for ixgbe

but I'm hitting other issues now.

/root/mcgray/dpdk-16.07/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/kni_misc.c:441:20: error: macro "alloc_netdev" passed 4 arguments, but takes just 3

I had already turned of KNI in my config file, so why is the dpdk-setup.sh even trying to build this stuff??

I don't need KNI as far as I know

I saw mention of backported kernel?

I guess my 16.7 is a few months old now, if I go and get another download will this all just go away?

Thanks

Sry, this stuff all a bit beyond my experience so far.



Martin Curran-Gray

next             reply	other threads:[~2016-11-02 16:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 16:19 martin_curran-gray [this message]
2016-11-02 16:30 ` Ferruh Yigit
2016-11-02 16:40   ` martin_curran-gray
  -- strict thread matches above, loose matches on Subject: below --
2016-06-12 15:30 [dpdk-dev] Can't build DPDK-16.04 on CentOS 6.8 Rosen, Rami
2016-06-15 15:57 ` [dpdk-dev] [PATCH] igb_uio: fix build with backported kernel Ferruh Yigit
2016-06-15 15:59   ` Ferruh Yigit
2016-06-16 15:45     ` Martinx - ジェームズ
2016-06-17  9:15       ` Ferruh Yigit
2016-06-21 14:12   ` 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=22C95CA62CBADB498D32A348F0F073BC269617BF@wcosexch02k.cos.is.keysight.com \
    --to=martin_curran-gray@keysight.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

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).