From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=z1x3GozWX90+j0eYAitY7Ci3QdbtHh+e3UEM5cWSmqA=; b=SW+jwHT+QlpHfhOpcGATJFmYUtWkPvteHUGVjECvKWUUqLjK3dp1fe1t+2b3JgU+BM FNG1sJbnW0wn+PWf3XhyUUhbKYZQMcsIBAhhM6VK8dieMnz+MQNh+8qVsG/WEm5kcLQh fN9Cn5PxjpxsnVw58JiCJMrRRx4tbVhtUGLIXDvp4TjfzNK+N2fb3csQmMLGbqDleG7r Xy0bBe0jI6eAriQYxkGKVNVuRQySITeyKSk9pLXCZgIEjs5x3AHhMwdqBTYSCj5RO5ej HWNCljNkzpBxZtbDnFgZyx5LZ+XuX+I93tkYXX9icYA5bhpojr+W11aH+BXHo5y+nRQ2 lL4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=z1x3GozWX90+j0eYAitY7Ci3QdbtHh+e3UEM5cWSmqA=; b=YAS3COytg1jfjtABdy4BnHI7mJ2irNHe4iIt7Hm5RBEi8hyP+A/OU9WTimE0+c8vCA pfmwQi7bBSyuyF2pZ95N/ORn2CEMosiRiR6yX5/7fQQ0y/d3rUe8dV1zMQk7d/gm37n6 g40X/r/viDgYWNAKf+/s8eSIHqKVZul0A168lRTnPoy7PX74aB93NRJbkgo29sm5mz3X OWLEKVQGFWOwWw1mxPPsZGNndcGXms1deO7wOoUSpoxXj1eUljl6DIvSrgw4VejemeJF dISgBC3TQDbjZyXhxLpQZEy7EgduWSrrl8th04VhjzblW2ke7syCJMBnKtL2ZNVj188d /FEw== X-Gm-Message-State: AMke39lUPSIc2ekMhnzwNZtwnYo1kVi9i1dojQ1/WOqizr0MGVf74YDG+sIJWnd5Z5gZ6VT0 X-Received: by 10.223.170.73 with SMTP id q9mr31730780wrd.13.1489484387905; Tue, 14 Mar 2017 02:39:47 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id t30sm13293862wra.55.2017.03.14.02.39.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Mar 2017 02:39:47 -0700 (PDT) From: Thomas Monjalon To: Raphael Cohn Cc: dev@dpdk.org Date: Tue, 14 Mar 2017 10:39:46 +0100 Message-ID: <3819926.kmXSVUIyKQ@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Compiling DPDK 17.02 with a Busybox-based tar X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Mar 2017 09:39:48 -0000 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.