DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, ashish.gupta@caviumnetworks.com, stable@dpdk.org
Subject: [dpdk-dev] [PATCH 3/4] devtools: test build of zlib PMD
Date: Wed, 13 Feb 2019 00:05:06 +0100	[thread overview]
Message-ID: <20190212230507.11793-4-thomas@monjalon.net> (raw)
In-Reply-To: <20190212230507.11793-1-thomas@monjalon.net>

The PMD zlib was not enabled in devtools/test-build.sh.
It is fixed by using the environment variable DPDK_DEP_ZLIB.

Fixes: 0c4e4c16b004 ("compress/zlib: introduce zlib PMD")
Cc: ashish.gupta@caviumnetworks.com
Cc: stable@dpdk.org

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 devtools/test-build.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/devtools/test-build.sh b/devtools/test-build.sh
index ace52a776..0511ae6d0 100755
--- a/devtools/test-build.sh
+++ b/devtools/test-build.sh
@@ -158,6 +158,8 @@ config () # <directory> <target> <options>
 		test "$DPDK_DEP_ZLIB" != y || \
 		sed -ri          's,(BNX2X_PMD=)n,\1y,' $1/.config
 		test "$DPDK_DEP_ZLIB" != y || \
+		sed -ri           's,(PMD_ZLIB=)n,\1y,' $1/.config
+		test "$DPDK_DEP_ZLIB" != y || \
 		sed -ri   's,(COMPRESSDEV_TEST=)n,\1y,' $1/.config
 		test "$DPDK_DEP_PCAP" != y || \
 		sed -ri               's,(PCAP=)n,\1y,' $1/.config
-- 
2.20.1

  parent reply	other threads:[~2019-02-12 23:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-12 23:05 [dpdk-dev] [PATCH 0/4] fix test of some build options Thomas Monjalon
2019-02-12 23:05 ` [dpdk-dev] [PATCH 1/4] mk: fix build of shared library with libbsd Thomas Monjalon
2019-02-12 23:05 ` [dpdk-dev] [PATCH 2/4] devtools: add libelf dependency to build test Thomas Monjalon
2019-02-12 23:05 ` Thomas Monjalon [this message]
2019-02-12 23:05 ` [dpdk-dev] [PATCH 4/4] devtools: fix test of some build options Thomas Monjalon
2019-02-13 18:22   ` Trahe, Fiona
2019-02-24 22:24 ` [dpdk-dev] [PATCH 0/4] " 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=20190212230507.11793-4-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=ashish.gupta@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --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).