From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Compiling DPDK 17.02 with a Busybox-based tar Date: Tue, 14 Mar 2017 10:39:46 +0100 Message-ID: <3819926.kmXSVUIyKQ@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Raphael Cohn Return-path: Received: from mail-wr0-f171.google.com (mail-wr0-f171.google.com [209.85.128.171]) by dpdk.org (Postfix) with ESMTP id 5FA5D2C1A for ; Tue, 14 Mar 2017 10:39:48 +0100 (CET) Received: by mail-wr0-f171.google.com with SMTP id u48so120079422wrc.0 for ; Tue, 14 Mar 2017 02:39:48 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2017-03-14 07:58, Raphael Cohn: > Hi, > > To compile DPDK on a system with Busybox tar installed, it's necessary to > make a small change to the build system:- > > sed -i -e '/--keep-newer-files/d' mk/rte.sdkinstall.mk > sed -i -e 's;--strip-components=1 \\;--strip-components=1;g' mk/ > rte.sdkinstall.mk > > I'm not sure whether the impact of this change fundamentally affects DPDK. > I'm a little surprised that tar is needed at all for a compile + install, > but I haven't investigated further. Is it being used to do a copy? Yes it is used to make a copy. It is a convenient one-liner. I am a bit surprised that you need to install DPDK with busybox. The busybox systems are generally cross-built and prepared out of the box, with the host tools. However, if you feel it is important to install DPDK on such target, you are welcome to propose a patch.