From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1168] [23.03-rc1] dpdk-next-crypto examples/fips_validation meson build error with gcc4.8.5 on Centos7.9
Date: Tue, 28 Feb 2023 06:29:33 +0000 [thread overview]
Message-ID: <bug-1168-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3832 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1168
Bug ID: 1168
Summary: [23.03-rc1] dpdk-next-crypto examples/fips_validation
meson build error with gcc4.8.5 on Centos7.9
Product: DPDK
Version: 23.03
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: chenyux.huang@intel.com
Target Milestone: ---
[git]
commit 666b5d8ddd36d269076296697bb79bfa6cfeff4f (HEAD -> for-main,
origin/for-main, origin/HEAD)
Author: Tejasree Kondoj <ktejasree@marvell.com>
Date: Fri Feb 24 11:26:11 2023 +0530
test/crypto: enable SG tests for cn10k
Removed PMD specific check in IPsec SG cases.
Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>
[OS version]
CentOS Linux 7 (Core)
CentOS79-64_K3.10.0_GCC4.8.5
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
[bad commit]
commit 12b10f60b6e5dcc1b24d334721dd11505d1e3c9a
Author: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Mon Feb 6 20:15:56 2023 +0530
examples/fips_validation: add SHAKE validation
Add support in fips_validation to parse SHAKE algorithms.
Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Acked-by: Brian Dooley <brian.dooley@intel.com>
[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]
Found ninja-1.10.2.git.kitware.jobserver-1 at /usr/local/bin/ninja
ninja: Entering directory `x86_64-native-linuxapp-gcc/'
[3045/3213] Compiling C object
examples/dpdk-fips_validation.p/fips_validation_main.c.o
FAILED: examples/dpdk-fips_validation.p/fips_validation_main.c.o
gcc -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_main.c.o -MF
examples/dpdk-fips_validation.p/fips_validation_main.c.o.d -o
examples/dpdk-fips_validation.p/fips_validation_main.c.o -c
../examples/fips_validation/main.c
../examples/fips_validation/main.c: In function ‘fips_mct_shake_test’:
../examples/fips_validation/main.c:2425:5: error: dereferencing type-punned
pointer will break strict-aliasing rules [-Werror=strict-aliasing]
(*(uint16_t *)rightmost % range);
^
cc1: all warnings being treated as errors
[3054/3213] Compiling C object app/test/dpdk-test.p/test_ring.c.o
ninja: build stopped: subcommand failed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 6094 bytes --]
reply other threads:[~2023-02-28 6:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1168-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 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.