From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 955] build failure in qos_sched example app
Date: Tue, 08 Mar 2022 08:15:34 +0000 [thread overview]
Message-ID: <bug-955-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=955
Bug ID: 955
Summary: build failure in qos_sched example app
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson --werror -Dexamples=all build && ninja -C build
[..]
examples/qos_sched/args.c: In function 'app_parse_args':
examples/qos_sched/args.c:413:28: error: implicit declaration of function
'RTE_BIT64'; did you mean 'RTE_BE64'? [-Werror=implicit-function-declaration]
413 | if (app_used_core_mask & RTE_BIT64(app_main_core)) {
| ^~~~~~~~~
| RTE_BE64
examples/qos_sched/args.c:413:28: error: nested extern declaration of
'RTE_BIT64' [-Werror=nested-externs]
cc1: all warnings being treated as errors
"""
Also reproduces with clang:
"""
$ meson --werror --buildtype=debugoptimized -Dexamples=all build && ninja -C
build
[..]
examples/qos_sched/args.c:413:28: error: implicit declaration of function
'RTE_BIT64' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
if (app_used_core_mask & RTE_BIT64(app_main_core)) {
^
examples/qos_sched/args.c:419:24: error: implicit declaration of function
'RTE_BIT64' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
app_used_core_mask |= RTE_BIT64(app_main_core);
^
2 errors generated.
"""
OS: Ubuntu 20.04.4
gcc: 9.3.0
clang: 10.0.0
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-03-08 8:15 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-955-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.