From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 557] Meson build DPDK with GCC11
Date: Thu, 15 Oct 2020 16:49:43 +0000 [thread overview]
Message-ID: <bug-557-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=557
Bug ID: 557
Summary: Meson build DPDK with GCC11
Product: DPDK
Version: unspecified
Hardware: ARM
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: dliu@iol.unh.edu
Target Milestone: ---
Hello everyone,
We have successfully added GCC11 to Fedora Rawhide, but when we are trying to
compile DPDK with GCC11. The compilation failed on an error showed below:
../app/test/test_graph_perf.c: In function ‘graph_init’:
../app/test/test_graph_perf.c:311:1: error: wrong number of arguments specified
for ‘access’ attribute
311 | {
| ^
../app/test/test_graph_perf.c:311:1: note: expected between 1 and 3, found 4
[2368/2483] Compiling C object
drivers/libtmp_rte_pmd_octeontx2_event.a.p/event_octeontx2_otx2_worker_dual.c.o
ninja: build stopped: subcommand failed.
Please let us know if there is anything we can do with this error.
Regards,
David
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-10-15 16:49 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-557-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).