From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 875] meson build fails on POWER9 with gcc 4.8.5
Date: Mon, 01 Nov 2021 16:53:02 +0000 [thread overview]
Message-ID: <bug-875-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=875
Bug ID: 875
Summary: meson build fails on POWER9 with gcc 4.8.5
Product: DPDK
Version: unspecified
Hardware: POWER
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
"""
$ meson --werror build-meson && ninja -C build-meson
The Meson build system
Version: 0.56.2
Source dir: /tmp/dpdk
Build dir: /tmp/dpdk/build-meson
Build type: native build
Program cat found: YES (/bin/cat)
Project name: DPDK
Project version: 21.11.0-rc1
C compiler for the host machine: ccache cc (gcc 4.8.5 "cc (GCC) 4.8.5 20150623
(Red Hat 4.8.5-36)")
C linker for the host machine: cc ld.bfd 2.27-34
Host machine cpu family: ppc64
Host machine cpu: ppc64le
Message: ## Building in Developer Mode ##
Program pkg-config found: YES (/bin/pkg-config)
Program check-symbols.sh found: YES (/tmp/dpdk/buildtools/check-symbols.sh)
Program options-ibverbs-static.sh found: YES
(/tmp/dpdk/buildtools/options-ibverbs-static.sh)
Program binutils-avx512-check.sh found: YES
(/tmp/dpdk/buildtools/binutils-avx512-check.sh)
Program python3 found: YES (/path/to/python3.8)
Program cat found: YES (/bin/cat)
Program ../buildtools/symlink-drivers-solibs.sh found: YES (/bin/sh
/tmp/dpdk/config/../buildtools/symlink-drivers-solibs.sh)
Checking for size of "void *" : 8
Checking for size of "void *" : 8
Library m found: YES
Library numa found: YES
Has header "numaif.h" : YES
Library libfdt found: NO
Library libexecinfo found: NO
Found pkg-config: /bin/pkg-config (0.27.1)
Run-time dependency libarchive found: NO (tried pkgconfig)
Run-time dependency libbsd found: NO (tried pkgconfig)
Run-time dependency libpcap found: NO (tried pkgconfig)
Library pcap found: YES
Has header "pcap.h" with dependency -lpcap: YES
Compiler for C supports arguments -Wextra: YES
config/meson.build:285: WARNING: Consider using the built-in warning_level
option instead of using "-Wextra".
Compiler for C supports arguments -Wcast-qual: YES
Compiler for C supports arguments -Wdeprecated: YES
Compiler for C supports arguments -Wformat: YES
Compiler for C supports arguments -Wformat-nonliteral: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -Wmissing-declarations: YES
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wnested-externs: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wsign-compare: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -Wwrite-strings: YES
Compiler for C supports arguments -Wno-address-of-packed-member: NO
Compiler for C supports arguments -Wno-packed-not-aligned: NO
Compiler for C supports arguments -Wno-missing-field-initializers: YES
Compiler for C supports arguments -mcpu=power9: NO
Checking if "Detect host CPU type" runs: YES
Compiler for C supports arguments -mcpu=power9: NO (cached)
Compiler for C supports arguments -mcpu=power8: YES
config/ppc/meson.build:95:16: ERROR: Problem encountered: Compiler does not
support POWER8 platform
A full log can be found at /tmp/dpdk/build-meson/meson-logs/meson-log.txt
"""
Caused by: 750196880843 ("config/ppc: select instruction set for IBM Power10")
The error doesn't reproduce with gcc 11.2.0, and doesn't reproduce with
-Dplatform=generic.
OS: RHEL 7.6
lscpu's model name: POWER9, altivec supported
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-11-01 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 16:53 bugzilla [this message]
2021-11-03 19:43 ` 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-875-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).