From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 984] [20.11] pmdinfogen build failure with gcc 4.8.5
Date: Mon, 28 Mar 2022 14:15:10 +0000 [thread overview]
Message-ID: <bug-984-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=984
Bug ID: 984
Summary: [20.11] pmdinfogen build failure with gcc 4.8.5
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson --werror --buildtype=debugoptimized build && ninja-build -C build
[..]
[5/2516] Compiling C object buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o
FAILED: buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o
clang -Ibuildtools/pmdinfogen/pmdinfogen.p -Ibuildtools/pmdinfogen
-I../../root/dpdk/buildtools/pmdinfogen -I. -I../../root/dpdk -Iconfig
-I../../root/dpdk/config -Ilib/librte_eal/include
-I../../root/dpdk/lib/librte_eal/include -Ilib/librte_eal/linux/include
-I../../root/dpdk/lib/librte_eal/linux/include -Ilib/librte_eal/x86/include
-I../../root/dpdk/lib/librte_eal/x86/include -Ilib/librte_pci
-I../../root/dpdk/lib/librte_pci -Xclang -fcolor-diagnostics -pipe
-D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O2 -g -MD -MQ
buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o -MF
buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o.d -o
buildtools/pmdinfogen/pmdinfogen.p/pmdinfogen.c.o -c
../../root/dpdk/buildtools/pmdinfogen/pmdinfogen.c
../../root/dpdk/buildtools/pmdinfogen/pmdinfogen.c:431:27: error: missing field
'hdr' initializer [-Werror,-Wmissing-field-initializers]
struct elf_info info = {0};
^
1 error generated.
[..]
"""
OS: CentOS Linux 7
gcc: 4.8.5
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-03-28 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 14:15 bugzilla [this message]
2022-04-04 10:29 ` [Bug 984] [19.11][20.11] pmdinfogen build failure with clang 3.4.2 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-984-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).