From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 920] [19.11.11] drivers/event/skeleton meson build failure with gcc 10.3.0 + debug on FreeBSD13.0/64
Date: Wed, 12 Jan 2022 08:09:59 +0000 [thread overview]
Message-ID: <bug-920-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=920
Bug ID: 920
Summary: [19.11.11] drivers/event/skeleton meson build failure
with gcc 10.3.0 + debug on FreeBSD13.0/64
Product: DPDK
Version: 19.11
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]:
87ed66bd94 (HEAD, tag: v19.11.11, origin/19.11)
[OS version]:
FreeBSD 13.0-RELEASE, kernel 4.18.0 ICC19.1.1
gcc version 10.3.0 (FreeBSD Ports Collection)
[Test Setup]:
echo "#define RTE_LIBRTE_PMD_SKELETON_EVENTDEV_DEBUG 1" >>config/rte_config.h
CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib -Dexamples=all
--buildtype=debugoptimized --default-library=static
x86_64-native-bsdapp-gcc+debug
ninja -j 10 -C x86_64-native-bsdapp-gcc+debug
[Notes]
1, Meson build 19.11 also failed with gcc10.3.0
[FreeBSD 13.0-RELEASE log as below]
ninja: Entering directory `x86_64-native-bsdapp-gcc+debug'
[1157/1594] Compiling C object
drivers/libtmp_rte_pmd_skeleton_event.a.p/event_skeleton_skeleton_eventdev.c.o
FAILED:
drivers/libtmp_rte_pmd_skeleton_event.a.p/event_skeleton_skeleton_eventdev.c.o
gcc -Idrivers/libtmp_rte_pmd_skeleton_event.a.p -Idrivers -I../drivers
-Idrivers/event/skeleton -I../drivers/event/skeleton -Ilib/librte_eventdev
-I../lib/librte_eventdev -I. -I.. -Iconfig -I../config
-Ilib/librte_eal/common/include -I../lib/librte_eal/common/include
-I../lib/librte_eal/freebsd/eal/include -Ilib/librte_eal/common
-I../lib/librte_eal/common -Ilib/librte_eal/common/include/arch/x86
-I../lib/librte_eal/common/include/arch/x86 -Ilib/librte_eal
-I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs
-Ilib/librte_ring -I../lib/librte_ring -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_meter -I../lib/librte_meter -Ilib/librte_hash -I../lib/librte_hash
-Ilib/librte_timer -I../lib/librte_timer -Ilib/librte_cryptodev
-I../lib/librte_cryptodev -Idrivers/bus/pci -I../drivers/bus/pci
-I../drivers/bus/pci/bsd -Ilib/librte_pci -I../lib/librte_pci
-Idrivers/bus/vdev -I../drivers/bus/vdev -fdiagnostics-color=always
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O2 -g -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-address-of-packed-member -Wno-packed-not-aligned
-Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE
-D__BSD_VISIBLE -fPIC -march=native -Wno-format-truncation -MD -MQ
drivers/libtmp_rte_pmd_skeleton_event.a.p/event_skeleton_skeleton_eventdev.c.o
-MF
drivers/libtmp_rte_pmd_skeleton_event.a.p/event_skeleton_skeleton_eventdev.c.o.d
-o
drivers/libtmp_rte_pmd_skeleton_event.a.p/event_skeleton_skeleton_eventdev.c.o
-c ../drivers/event/skeleton/skeleton_eventdev.c
In file included from ../lib/librte_eal/common/include/rte_debug.h:17,
from ../drivers/event/skeleton/skeleton_eventdev.c:14:
../drivers/event/skeleton/skeleton_eventdev.c: In function
'skeleton_eventdev_remove':
../lib/librte_eal/common/include/rte_log.h:336:3: error: '%s' directive
argument is null [-Werror=format-overflow=]
336 | rte_log(RTE_LOG_ ## l, \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
337 | RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/event/skeleton/skeleton_eventdev.h:13:2: note: in expansion of macro
'RTE_LOG'
13 | RTE_LOG(level, PMD, "%s(): " fmt "\n", __func__, ## args)
| ^~~~~~~
../drivers/event/skeleton/skeleton_eventdev.c:467:2: note: in expansion of
macro 'PMD_DRV_LOG'
467 | PMD_DRV_LOG(INFO, "Closing %s on NUMA node %d", name,
rte_socket_id());
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
[1166/1594] Compiling C object
drivers/libtmp_rte_pmd_octeontx2_event.a.p/event_octeontx2_otx2_worker_dual.c.o
ninja: build stopped: subcommand failed.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-01-12 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 8:09 bugzilla [this message]
2022-02-11 10:22 ` 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-920-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).