From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8AE7DA0589; Fri, 27 Mar 2020 11:35:52 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 70B5E1C0AE; Fri, 27 Mar 2020 11:35:52 +0100 (CET) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id D0C11F3E for ; Fri, 27 Mar 2020 11:35:50 +0100 (CET) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 978CC751; Fri, 27 Mar 2020 06:35:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Fri, 27 Mar 2020 06:35:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=EtM5AXuW8iWBfbp3oF67H6n1NU3a0mg2lg3yWjnOWGk=; b=cIrPzGvGcHvP 3vrsKq/EeV9Pfz4MbYzcxH8qRFtRXqVL0XMxiPVvhO+t63DIRmabHwIXsDpa8e9V lhy2lANN5Awqn0DqdfQuebqQlyCBrRdjcOMYzRhWODgDvy51eQQBuh2zSzLyJERE ihfisoPtThKj6ubx5dLvBsJoMeZPANk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=EtM5AXuW8iWBfbp3oF67H6n1NU3a0mg2lg3yWjnOW Gk=; b=K8f0Zyx9yc296/BWkkR8NFSWOmmq4aC7hRhdnt0GEhe6RnsSaOKiAVtv1 g3SK/H9oBNmgpTCCTXCKthh4BB6qHvpZpxg6mx0cUjauDDkYWPS1G2gXpguq+kKy 2ordRCxQxuSUpbDxD2FS3F/5+1F1Kb33qpbt7B640KZd37YZItzn8xlEbwa/hK0C W2H0wO4WC/BsGH5M3GfBigcqK2dbof+V6Xo06YnQlkTrOwgpIiGElyvm3OVAEp6V tMzbEkrlnyJ5OGIJXbqNgpOx+V129uzJHx+cuMWcwy8vB2mSdSVwqvguPeBZ2WL5 rkzpVjlnaIJrh4Vy9K5xbPi1aB0MQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudehledgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtqhertddttddunecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghdpvgigthhvrghrshdrmhhknecukfhppeejjedrudef gedrvddtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 255F5306C201; Fri, 27 Mar 2020 06:35:48 -0400 (EDT) From: Thomas Monjalon To: Tom Barbette Cc: dev@dpdk.org, Matthew Hall Date: Fri, 27 Mar 2020 11:35:47 +0100 Message-ID: <1935321.K71DO8KEF6@xps> In-Reply-To: <83f48ac2-cf68-dc19-dc6b-d775e0b3de4e@kth.se> References: <83f48ac2-cf68-dc19-dc6b-d775e0b3de4e@kth.se> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] Impossible to build external application if user build DPDK with "make config" 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 27/03/2020 10:14, Tom Barbette: > CC'ing original participants as I don't see a way out of this. >=20 > Le 12/03/2020 =E0 13:04, Tom Barbette a =E9crit : > > Hi all, > >=20 > > If the user follows the quick guide=20 > > (http://core.dpdk.org/doc/quick-start/) DPDK will be compiled in the=20 > > "build" folder. > >=20 > > However, external applications will always fail to build because=20 > > RTE_SDK_BIN is strictly defined as $RTE_SDK/$RTE_TARGET, and=20 > > mk/internal/rte.extvars.mk needs to find .config in $RTE_SDK_BIN. > >=20 > > Therefore please apply the patch at: > > http://patchwork.dpdk.org/patch/9991/ that allows external apps to=20 > > override $RTE_SDK_BIN. > >=20 > > Or (less preferable) modify the quick start guide to use something more= =20 > > standard that allows to build with external apps (eg use the menu or=20 > > propose "make config T=3Dx86_64-native-linuxapp-gcc=20 > > O=3Dx86_64-native-linuxapp-gcc" instead). It's much easier for external= =20 > > apps maintainer to refer to the DPDK tutorial for DPDK installation. I don't understand the issue. =46irst of all, the external application should link an installed DPDK. Then you should be able to set $RTE_SDK and $RTE_TARGET to fit the installation directories. Just checked doc/guides/linux_gsg/build_dpdk.rst I see the whole build process with make is not correctly documented. It should be: 1/ make defconfig or make config T=3Dx86_64-native-linux-gcc O=3Dmybuild 2/ make -j4 O=3Dmybuild 3/ make install O=3Dmybuild DESTDIR=3Dmyinstall prefix=3D 4/ RTE_SDK=3D$(pwd)/myinstall/share/dpdk RTE_TARGET=3Dx86_64-native-linux-g= cc make -C myapp Please can you confirm it works?