From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH] tools/sppc: add liblua5.x-dev installation
Date: Fri, 15 Feb 2019 02:42:31 +0900 [thread overview]
Message-ID: <20190214174231.6106-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Compilation of pktgen is failed if `lua.h` is not installed. It is
included in `liblua5.x-dev` in Ubuntu, so add the entry in the sequence
of `apt-get`.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
tools/sppc/build/ubuntu/pktgen/Dockerfile.16.04 | 1 +
tools/sppc/build/ubuntu/pktgen/Dockerfile.18.04 | 1 +
tools/sppc/build/ubuntu/pktgen/Dockerfile.latest | 1 +
3 files changed, 3 insertions(+)
diff --git a/tools/sppc/build/ubuntu/pktgen/Dockerfile.16.04 b/tools/sppc/build/ubuntu/pktgen/Dockerfile.16.04
index dac5a2a..4c4ae49 100644
--- a/tools/sppc/build/ubuntu/pktgen/Dockerfile.16.04
+++ b/tools/sppc/build/ubuntu/pktgen/Dockerfile.16.04
@@ -30,6 +30,7 @@ RUN apt-get update && apt-get install -y \
libarchive-dev \
linux-headers-$(uname -r) \
libpcap-dev \
+ liblua5*-dev \
pkg-config \
wget \
&& apt-get clean \
diff --git a/tools/sppc/build/ubuntu/pktgen/Dockerfile.18.04 b/tools/sppc/build/ubuntu/pktgen/Dockerfile.18.04
index 6a0640d..1103cdc 100644
--- a/tools/sppc/build/ubuntu/pktgen/Dockerfile.18.04
+++ b/tools/sppc/build/ubuntu/pktgen/Dockerfile.18.04
@@ -30,6 +30,7 @@ RUN apt-get update && apt-get install -y \
libarchive-dev \
linux-headers-$(uname -r) \
libpcap-dev \
+ liblua5*-dev \
pkg-config \
wget \
&& apt-get clean \
diff --git a/tools/sppc/build/ubuntu/pktgen/Dockerfile.latest b/tools/sppc/build/ubuntu/pktgen/Dockerfile.latest
index 3f0508d..5ff3e64 100644
--- a/tools/sppc/build/ubuntu/pktgen/Dockerfile.latest
+++ b/tools/sppc/build/ubuntu/pktgen/Dockerfile.latest
@@ -30,6 +30,7 @@ RUN apt-get update && apt-get install -y \
libarchive-dev \
linux-headers-$(uname -r) \
libpcap-dev \
+ liblua5*-dev \
pkg-config \
wget \
&& apt-get clean \
--
2.7.4
reply other threads:[~2019-02-14 17:42 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=20190214174231.6106-1-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--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).