From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 683] librte_pipeline build failures on CentOS 7
Date: Wed, 21 Apr 2021 07:36:07 +0000 [thread overview]
Message-ID: <bug-683-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=683
Bug ID: 683
Summary: librte_pipeline build failures on CentOS 7
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
CC: cristian.dumitrescu@intel.com
Target Milestone: ---
```
$ meson --werror --buildtype=release build && ninja-build -C build
[555/2604] Compiling C object
lib/librte_pipeline.a.p/librte_pipeline_rte_swx_pipeline.c.o
FAILED: lib/librte_pipeline.a.p/librte_pipeline_rte_swx_pipeline.c.o
ccache cc -Ilib/librte_pipeline.a.p -Ilib -I../lib -Ilib/librte_pipeline
-I../lib/librte_pipeline -I. -I.. -Iconfig -I../config -Ilib/librte_eal/include
-I../lib/librte_eal/include -Ilib/librte_eal/linux/include
-I../lib/librte_eal/linux/include -Ilib/librte_eal/x86/include
-I../lib/librte_eal/x86/include -Ilib/librte_eal/common
-I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal
-Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_metrics
-I../lib/librte_metrics -Ilib/librte_telemetry -I../lib/librte_telemetry
-Ilib/librte_port -I../lib/librte_port -Ilib/librte_ethdev
-I../lib/librte_ethdev -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_meter -I../lib/librte_meter
-Ilib/librte_sched -I../lib/librte_sched -Ilib/librte_ip_frag
-I../lib/librte_ip_frag -Ilib/librte_hash -I../lib/librte_hash -Ilib/librte_rcu
-I../lib/librte_rcu -Ilib/librte_cryptodev -I../lib/librte_cryptodev
-Ilib/librte_eventdev -I../lib/librte_eventdev -Ilib/librte_timer
-I../lib/librte_timer -Ilib/librte_kni -I../lib/librte_kni -Ilib/librte_pci
-I../lib/librte_pci -Ilib/librte_table -I../lib/librte_table -Ilib/librte_lpm
-I../lib/librte_lpm -Ilib/librte_acl -I../lib/librte_acl -pipe
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O3 -include rte_config.h
-Wextra -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 -fPIC
-march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -MD -MQ
lib/librte_pipeline.a.p/librte_pipeline_rte_swx_pipeline.c.o -MF
lib/librte_pipeline.a.p/librte_pipeline_rte_swx_pipeline.c.o.d -o
lib/librte_pipeline.a.p/librte_pipeline_rte_swx_pipeline.c.o -c
../lib/librte_pipeline/rte_swx_pipeline.c
../lib/librte_pipeline/rte_swx_pipeline.c: In function 'instr_translate':
../lib/librte_pipeline/rte_swx_pipeline.c:4202:30: error: 'src_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->alu.src.struct_id = (uint8_t)src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:4181:26: note: 'src_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:4216:29: error: 'dst_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->alu.dst.struct_id = (uint8_t)dst_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:4181:11: note: 'dst_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3966:30: error: 'src_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->alu.src.struct_id = (uint8_t)src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3945:26: note: 'src_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3980:29: error: 'dst_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->alu.dst.struct_id = (uint8_t)dst_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3945:11: note: 'dst_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3913:30: error: 'src_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->alu.src.struct_id = (uint8_t)src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3892:26: note: 'src_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3927:29: error: 'dst_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->alu.dst.struct_id = (uint8_t)dst_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3892:11: note: 'dst_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3648:30: error: 'src_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->mov.src.struct_id = (uint8_t)src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3627:26: note: 'src_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3662:29: error: 'dst_struct_id' may
be used uninitialized in this function [-Werror=maybe-uninitialized]
instr->mov.dst.struct_id = (uint8_t)dst_struct_id;
^
../lib/librte_pipeline/rte_swx_pipeline.c:3627:11: note: 'dst_struct_id' was
declared here
uint32_t dst_struct_id, src_struct_id;
^
cc1: all warnings being treated as errors
[588/2604] Compiling C object
lib/librte_pipeline.a.p/librte_pipeline_rte_table_action.c.o
ninja: build stopped: subcommand failed.
```
OS: CentOS 7.9.2009
gcc: 4.8.5
meson: 0.55.1
ninja-build: 1.10.2
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-04-21 7:36 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-683-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.