From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH] tools/sppc: fix compile error of spp_pcap
Date: Wed, 31 Jul 2019 14:12:45 +0900 [thread overview]
Message-ID: <20190731051245.37226-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
Compiling spp_pcap requires `iblz4-dev` and `liblz4-tool`, but not
including in Dockerfiles of SPP and failed to compile. This patch is
to fix the issue.
Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
---
tools/sppc/build/ubuntu/spp/Dockerfile.16.04 | 2 ++
tools/sppc/build/ubuntu/spp/Dockerfile.18.04 | 2 ++
tools/sppc/build/ubuntu/spp/Dockerfile.latest | 2 ++
3 files changed, 6 insertions(+)
diff --git a/tools/sppc/build/ubuntu/spp/Dockerfile.16.04 b/tools/sppc/build/ubuntu/spp/Dockerfile.16.04
index 27311ea..a928ac4 100644
--- a/tools/sppc/build/ubuntu/spp/Dockerfile.16.04
+++ b/tools/sppc/build/ubuntu/spp/Dockerfile.16.04
@@ -32,6 +32,8 @@ RUN apt-get update && apt-get install -y \
libarchive-dev \
linux-headers-$(uname -r) \
libpcap-dev \
+ liblz4-dev \
+ liblz4-tool \
pkg-config \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*
diff --git a/tools/sppc/build/ubuntu/spp/Dockerfile.18.04 b/tools/sppc/build/ubuntu/spp/Dockerfile.18.04
index afd33f9..7a7c06b 100644
--- a/tools/sppc/build/ubuntu/spp/Dockerfile.18.04
+++ b/tools/sppc/build/ubuntu/spp/Dockerfile.18.04
@@ -33,6 +33,8 @@ RUN apt-get update && apt-get install -y \
libarchive-dev \
linux-headers-$(uname -r) \
libpcap-dev \
+ liblz4-dev \
+ liblz4-tool \
pkg-config \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*
diff --git a/tools/sppc/build/ubuntu/spp/Dockerfile.latest b/tools/sppc/build/ubuntu/spp/Dockerfile.latest
index 380eb18..6f87cd1 100644
--- a/tools/sppc/build/ubuntu/spp/Dockerfile.latest
+++ b/tools/sppc/build/ubuntu/spp/Dockerfile.latest
@@ -33,6 +33,8 @@ RUN apt-get update && apt-get install -y \
libarchive-dev \
linux-headers-$(uname -r) \
libpcap-dev \
+ liblz4-dev \
+ liblz4-tool \
pkg-config \
&& apt-get clean \
&& rm -rf /var/lib/apt/lists/*
--
2.17.1
reply other threads:[~2019-07-31 5:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190731051245.37226-1-yasufum.o@gmail.com \
--to=yasufum.o@gmail.com \
--cc=ferruh.yigit@intel.com \
--cc=spp@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).