DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	Beilei Xing <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] meson build fail for i40e
Date: Thu, 3 May 2018 18:59:48 +0530	[thread overview]
Message-ID: <20a762ac-2beb-2de3-a09d-1c667694f2d5@nxp.com> (raw)

Bruce, Beilei,

Can you help me here?

Build targets in project: 263
Found ninja-1.8.2 at /usr/bin/ninja
[585/940] Compiling C object 
'drivers/net/i40e/i40e_avx2_lib@sta/i40e_rxtx_vec_avx2.c.o'.
FAILED: drivers/net/i40e/i40e_avx2_lib@sta/i40e_rxtx_vec_avx2.c.o
ccache cc  -Idrivers/net/i40e/i40e_avx2_lib@sta -Idrivers/net/i40e 
-I../drivers/net/i40e -Ilib/librte_ethdev -I../lib/librte_ethdev 
-Iconfig -I../config -I. -I../ -Ilib/librte_eal/common/include/arch/x86 
-I../lib/librte_eal/common/include/arch/x86 
-Ilib/librte_eal/common/include -I../lib/librte_eal/common/include 
-Ilib/librte_eal/common -I../lib/librte_eal/common 
-Ilib/librte_eal/linuxapp/eal/../../../librte_compat 
-I../lib/librte_eal/linuxapp/eal/../../../librte_compat 
-I../lib/librte_eal/linuxapp/eal/include -Ilib/librte_eal 
-I../lib/librte_eal -Ilib/librte_compat -I../lib/librte_compat 
-Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf 
-I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool 
-Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_kvargs 
-I../lib/librte_kvargs -Ilib/librte_hash -I../lib/librte_hash 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -O3 -include rte_config.h -Wsign-compare -Wcast-qual 
-Wno-address-of-packed-member -Wno-format-truncation -fPIC -mavx2 -MMD 
-MQ 'drivers/net/i40e/i40e_avx2_lib@sta/i40e_rxtx_vec_avx2.c.o' -MF 
'drivers/net/i40e/i40e_avx2_lib@sta/i40e_rxtx_vec_avx2.c.o.d' -o 
'drivers/net/i40e/i40e_avx2_lib@sta/i40e_rxtx_vec_avx2.c.o' -c 
../drivers/net/i40e/i40e_rxtx_vec_avx2.c
In file included from ../drivers/net/i40e/i40e_rxtx_vec_avx2.c:40:0:
../drivers/net/i40e/i40e_ethdev.h:888:42: error: 
‘I40E_PFQF_HKEY_MAX_INDEX’ undeclared here (not in a function); did you 
mean ‘I40E_VFQF_HKEY_MAX_INDEX’?
   uint8_t key[(I40E_VFQF_HKEY_MAX_INDEX > I40E_PFQF_HKEY_MAX_INDEX ?
                                           ^~~~~~~~~~~~~~~~~~~~~~~~
                                           I40E_VFQF_HKEY_MAX_INDEX
cc1: warning: unrecognized command line option 
‘-Wno-address-of-packed-member’
[590/940] Compiling C object 
'drivers/net/sfc/base/sfc_base@sta/efx_filter.c.o'.
ninja: build stopped: subcommand failed.

--

This is the ninja configuration:

--->8---
The Meson build system
Version: 0.44.0
Source dir: /home/shreyansh/build/DPDK/03_dpdk
Build dir: /home/shreyansh/build/DPDK/03_dpdk/generic_build
Build type: native build
Project name: DPDK
Native C compiler: ccache cc (gcc 7.3.0)
Build machine cpu family: x86_64
Build machine cpu: x86_64
Library numa found: YES
Has header "numaif.h": YES
Library bsd found: NO
--->8---

And I am pretty sure it was appearing on gcc 7.2 as well.

             reply	other threads:[~2018-05-03 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 13:29 Shreyansh Jain [this message]
2018-05-03 15:49 ` Bruce Richardson
2018-05-05 18:12   ` Shreyansh Jain

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=20a762ac-2beb-2de3-a09d-1c667694f2d5@nxp.com \
    --to=shreyansh.jain@nxp.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.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).