From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1103] [dpdk-next-crypto] examples/fips_validation meson build failed on centos7.9 with gcc4.8
Date: Thu, 13 Oct 2022 08:31:16 +0000 [thread overview]
Message-ID: <bug-1103-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=1103
Bug ID: 1103
Summary: [dpdk-next-crypto] examples/fips_validation meson
build failed on centos7.9 with gcc4.8
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: daxuex.gao@intel.com
Target Milestone: ---
[DPDK version]:
commit 60f48e581fe74e4be856363364a56df253a6655a
Author: Nic Chautru <nicolas.chautru@intel.com>
Date: Wed Oct 12 10:59:29 2022 -0700
baseband/acc: add descriptor index helpers
Added set of helper functions used through the code to
track descriptor indexes in a queue ring.
Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
[OS version]:
centos7.9/3.10.0-1160.el7.x86_64
GCC Version: gcc 4.8.5 20150623
[Test Setup]:
CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all
--default-library=static x86_64-native-linuxapp-gcc
ninja -j 10 -C x86_64-native-linuxapp-gcc
[Error log]
ninja: Entering directory `x86_64-native-linuxapp-gcc'
[3418/3567] Compiling C object
examples/dpdk-fips_validation.p/fips_validation_fips_validation_rsa.c.o
FAILED: examples/dpdk-fips_validation.p/fips_validation_fips_validation_rsa.c.o
cc -Iexamples/dpdk-fips_validation.p -Iexamples -I../examples
-Iexamples/fips_validation -I../examples/fips_validation -I../examples/common
-I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include
-Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include
-I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal
-I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics
-Ilib/telemetry -I../lib/telemetry -Ilib/mempool -I../lib/mempool -Ilib/ring
-I../lib/ring -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/ethdev
-I../lib/ethdev -Ilib/meter -I../lib/meter -Ilib/cmdline -I../lib/cmdline
-Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include
rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral
-Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
-Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes
-Wundef -Wwrite-strings -Wno-missing-field-initializers -D_GNU_SOURCE
-march=native -DUSE_OPENSSL -DALLOW_EXPERIMENTAL_API -MD -MQ
examples/dpdk-fips_validation.p/fips_validation_fips_validation_rsa.c.o -MF
examples/dpdk-fips_validation.p/fips_validation_fips_validation_rsa.c.o.d -o
examples/dpdk-fips_validation.p/fips_validation_fips_validation_rsa.c.o -c
../examples/fips_validation/fips_validation_rsa.c
../examples/fips_validation/fips_validation_rsa.c:8:24: fatal error:
sys/random.h: No such file or directory
#include <sys/random.h>
^
compilation terminated.
[3427/3567] Compiling C object app/test/dpdk-test.p/test_ring.c.o
ninja: build stopped: subcommand failed.
[bad commit]:
commit 2ca8e8e09377db7fa03670c0c34cdcaef2f5fe79
Author: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Wed Oct 12 11:42:36 2022 +0530
examples/fips_validation: add asymmetric validation
Add support for asymmetric crypto validation starting with RSA.
For the generation of crypto values which is multiprecision in
math, openssl library is used only for this purpose.
Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Acked-by: Brian Dooley <brian.dooley@intel.com>
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-10-13 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 8:31 bugzilla [this message]
2022-10-20 2:30 ` bugzilla
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=bug-1103-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).