From: Thomas Monjalon <thomas@monjalon.net>
To: radu.nicolau@intel.com, konstantin.ananyev@intel.com,
bruce.richardson@intel.com, ferruh.yigit@intel.com,
wenzhuo.lu@intel.com
Cc: michael.j.glynn@intel.com, dev@dpdk.org
Subject: build error in ixgbe_crypto_capabilities_get on SLES
Date: Sun, 05 Nov 2017 22:15:54 +0100 [thread overview]
Message-ID: <1703648.CeQUIMCXzx@xps> (raw)
In-Reply-To: <5d8929$51o63t@orsmga005.jf.intel.com>
Hi,
I think we have a compilation error in ixgbe IPsec for more than one week.
Someone to fix it please?
05/11/2017 21:11, sys_stv@intel.com:
> Failure #1
> SUSE11SP2_64 / Linux 3.0.13-0 / GCC 4.5.1
> Config: x86_64-native-linuxapp-gcc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y,
> CONFIG_RTE_LIBRTE_PMD_QAT=y,
> CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
> CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y
>
> SYMLINK-FILE include/rte_pmd_ixgbe.h PMDINFO ixgbe_ethdev.o.pmd.c LD ixgbe_ethdev.oDPDK/drivers/net/ixgbe/ixgbe_ipsec.c: In function ‘ixgbe_crypto_capabilities_get’:
> DPDK/drivers/net/ixgbe/ixgbe_ipsec.c:579:4: error: unknown field ‘ipsec’ specified in initializer
> compilation terminated due to -Wfatal-errors.
>
> Failure #2
> SUSE11SP2_64 / Linux 3.0.13-0 / ICC 16.0.2
> Config: x86_64-native-linuxapp-icc
> CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> CONFIG_RTE_NIC_BYPASS=y,
> CONFIG_RTE_BUILD_SHARED_LIB=y,
> CONFIG_RTE_LIBRTE_VHOST=y,
> CONFIG_RTE_LIBRTE_PMD_QAT=y,
> CONFIG_RTE_LIBRTE_PMD_AESNI_GCM=y,
> CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y
>
> SYMLINK-FILE include/rte_pmd_ixgbe.h PMDINFO ixgbe_ethdev.o.pmd.c LD ixgbe_ethdev.oDPDK/drivers/net/ixgbe/ixgbe_ipsec.c: In function ‘ixgbe_crypto_capabilities_get’:
> DPDK/drivers/net/ixgbe/ixgbe_ipsec.c:579:4: error: unknown field ‘ipsec’ specified in initializer
> compilation terminated due to -Wfatal-errors.
parent reply other threads:[~2017-11-05 21:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5d8929$51o63t@orsmga005.jf.intel.com>]
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=1703648.CeQUIMCXzx@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=michael.j.glynn@intel.com \
--cc=radu.nicolau@intel.com \
--cc=wenzhuo.lu@intel.com \
/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.