From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 897] [20.11.4-rc1] librte_eal/windows cross build failure with gcc 11 on Fedora 35
Date: Wed, 08 Dec 2021 16:29:55 +0000 [thread overview]
Message-ID: <bug-897-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=897
Bug ID: 897
Summary: [20.11.4-rc1] librte_eal/windows cross build failure
with gcc 11 on Fedora 35
Product: DPDK
Version: 20.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson --werror --buildtype=debugoptimized --cross-file config/x86/cross-mingw
-Dexamples=helloworld /tmp/build
[..]
/usr/lib/gcc/x86_64-w64-mingw32/11.2.1/../../../../x86_64-w64-mingw32/bin/ld:
lib/librte_eal.a.p/librte_eal_windows_eal_mp.c.obj: in function
`eal_dev_hotplug_request_to_primary':
/tmp/build/../../root/dpdk/lib/librte_eal/windows/eal_mp.c:111: multiple
definition of `eal_dev_hotplug_request_to_primary';
lib/librte_eal.a.p/librte_eal_common_hotplug_mp.c.obj:/tmp/build/../../root/dpdk/lib/librte_eal/common/hotplug_mp.c:366:
first defined here
/usr/lib/gcc/x86_64-w64-mingw32/11.2.1/../../../../x86_64-w64-mingw32/bin/ld:
lib/librte_eal.a.p/librte_eal_windows_eal_mp.c.obj:/tmp/build/../../root/dpdk/lib/librte_eal/windows/eal_mp.c:111:
multiple definition of `eal_dev_hotplug_request_to_secondary';
lib/librte_eal.a.p/librte_eal_common_hotplug_mp.c.obj:/tmp/build/../../root/dpdk/lib/librte_eal/common/hotplug_mp.c:394:
first defined here
collect2: error: ld returned 1 exit status
"""
C compiler for the host machine: x86_64-w64-mingw32-gcc (gcc 11.2.1
"x86_64-w64-mingw32-gcc (GCC) 11.2.1 20210728 (Fedora MinGW 11.2.1-3.fc35)")
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-12-08 16: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-897-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).