From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, bluca@debian.org, aconole@redhat.com,
stable@dpdk.org, Michael Santana <maicolgabriel@hotmail.com>
Subject: [dpdk-stable] [PATCH 2/2] ci: use meson 0.47.1
Date: Thu, 9 Jan 2020 13:59:16 +0100 [thread overview]
Message-ID: <20200109125916.32073-2-david.marchand@redhat.com> (raw)
In-Reply-To: <20200109125916.32073-1-david.marchand@redhat.com>
meson 0.53.0 has a compatibility issue [1] with the python 3.5.2 that comes
in Ubuntu 16.04.
On the other hand, the minimal version supported in dpdk is 0.47.1.
Stick to this version to avoid getting hit by regressions in meson latest
shiny release.
1: https://github.com/mesonbuild/meson/issues/6427
Cc: stable@dpdk.org
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
.ci/linux-setup.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.ci/linux-setup.sh b/.ci/linux-setup.sh
index dfb9d4a20..38bb88e15 100755
--- a/.ci/linux-setup.sh
+++ b/.ci/linux-setup.sh
@@ -1,7 +1,7 @@
#!/bin/sh -xe
# need to install as 'root' since some of the unit tests won't run without it
-sudo python3 -m pip install --upgrade meson
+sudo python3 -m pip install --upgrade 'meson==0.47.1'
# setup hugepages
cat /proc/meminfo
--
2.23.0
next prev parent reply other threads:[~2020-01-09 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 12:59 [dpdk-stable] [PATCH 1/2] build: fix libm detection in meson David Marchand
2020-01-09 12:59 ` David Marchand [this message]
2020-01-09 13:09 ` [dpdk-stable] [PATCH 2/2] ci: use meson 0.47.1 Bruce Richardson
2020-01-09 14:16 ` Aaron Conole
2020-01-09 13:09 ` [dpdk-stable] [PATCH 1/2] build: fix libm detection in meson Bruce Richardson
2020-01-09 14:08 ` David Marchand
2020-01-09 14:17 ` Aaron Conole
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=20200109125916.32073-2-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=stable@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).