From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
techboard@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/1] Update minimum required meson version
Date: Mon, 12 Sep 2022 18:07:46 +0100 [thread overview]
Message-ID: <20220912170747.3128065-1-bruce.richardson@intel.com> (raw)
Following some brief discussion on the dev list[1], here is a patch
to update the minimum meson version for DPDK to 0.53. The update
itself is fairly smooth, but, at least in my testing, it exposes some
issues with objdump not recognising the debug symbols from some clang
binaries. When building, one may see warnings like:
objdump: Warning: Unrecognized form: 0x22
These warnings were not previously visible with the 0.49 meson version
as the symbol checks were only run in "developer_mode" and auto-
detection of developer mode was limited to version 0.53 or later, due
to use of the "fs" meson module.
[1] http://inbox.dpdk.org/dev/CAOE1vsNoDP0oOLkj2J4LRttXxTL7F4w1sd=KHGOWSvu+onZGFw@mail.gmail.com/
Bruce Richardson (1):
build: increase minimum meson version to 0.53
.ci/linux-setup.sh | 2 +-
doc/guides/linux_gsg/sys_reqs.rst | 2 +-
doc/guides/prog_guide/build-sdk-meson.rst | 2 +-
drivers/common/mlx5/linux/meson.build | 2 +-
meson.build | 8 +++-----
5 files changed, 7 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2022-09-12 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 17:07 Bruce Richardson [this message]
2022-09-12 17:07 ` [PATCH 1/1] build: increase minimum meson version to 0.53 Bruce Richardson
2022-10-07 13:17 ` David Marchand
2022-10-07 14:11 ` Bruce Richardson
2022-10-07 15:26 ` David Marchand
2022-10-07 15:34 ` Bruce Richardson
2022-10-07 15:49 ` David Marchand
2022-10-07 16:24 ` [PATCH v2] build: increase minimum meson version to 0.53.2 Bruce Richardson
2022-10-07 19:13 ` David Marchand
2022-10-10 5:23 ` Tu, Lijuan
2022-10-10 7:48 ` David Marchand
2022-10-13 12:51 ` Tu, Lijuan
2022-10-10 14:53 ` David Marchand
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=20220912170747.3128065-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=lylavoie@iol.unh.edu \
--cc=techboard@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).