DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] fix test-meson-builds for older distros
Date: Wed, 10 Apr 2019 21:52:21 +0100	[thread overview]
Message-ID: <20190410205224.69977-1-bruce.richardson@intel.com> (raw)
Message-ID: <20190410205221.tWrH1eEdYkusa0nw6njq_SxAdnh7dwJ0KB604iGQs0M@z> (raw)

In order to ensure good test coverage, we sometimes need to run builds
on distros with older compilers, such as gcc 4.8 on RHEL/Centos 7. This
patchset does a small amount of clean-up to test-meson-builds.sh script
to allow it to be used for such gcc builds.

Bruce Richardson (3):
  devtools/test-meson-builds: skip missing compilers
  devtools/test-meson-builds: support older compilers
  devtools/test-meson-builds: fix bash-isms

 devtools/test-meson-builds.sh | 21 ++++++++++++++-------
 1 file changed, 14 insertions(+), 7 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-04-10 20:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 20:52 Bruce Richardson [this message]
2019-04-10 20:52 ` Bruce Richardson
2019-04-10 20:52 ` [dpdk-dev] [PATCH 1/3] devtools/test-meson-builds: skip missing compilers Bruce Richardson
2019-04-10 20:52   ` Bruce Richardson
2019-04-17 14:59   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-04-17 14:59     ` Thomas Monjalon
2019-04-17 15:04     ` Bruce Richardson
2019-04-17 15:04       ` Bruce Richardson
2019-04-10 20:52 ` [dpdk-dev] [PATCH 2/3] devtools/test-meson-builds: support older compilers Bruce Richardson
2019-04-10 20:52   ` Bruce Richardson
2019-04-10 20:52 ` [dpdk-dev] [PATCH 3/3] devtools/test-meson-builds: fix bash-isms Bruce Richardson
2019-04-10 20:52   ` Bruce Richardson
2019-04-11  8:48 ` [dpdk-dev] [PATCH 0/3] fix test-meson-builds for older distros Luca Boccassi
2019-04-11  8:48   ` Luca Boccassi
2019-04-17 15:17   ` Thomas Monjalon
2019-04-17 15:17     ` Thomas Monjalon

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=20190410205224.69977-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --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).