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 8E481A057C; Fri, 27 Mar 2020 16:06:27 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1BBE11C21E; Fri, 27 Mar 2020 16:06:27 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 985041C1D3 for ; Fri, 27 Mar 2020 16:06:25 +0100 (CET) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 112995C0234; Fri, 27 Mar 2020 11:06:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Fri, 27 Mar 2020 11:06:25 -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=C8d42+/qfS/X9BYw+4+Di0wrxFSzEOGthYiPrkpv2J0=; b=exiIvSa9TBkW kh8iajXZ8BJq/QG7CyU7o54O/XDHg6UI9wxlonoW7/IBTQDmvPjWlz7YXn1FWoK8 4MN0aPFsyyNICv8byzoKXakH2UTElV7YTUZMOVFLiRO+JGgjTD1/rTCwghW2DiwQ NwEAFXXpMYKlC9qJJ2SVMBdTWWV1lkc= 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=C8d42+/qfS/X9BYw+4+Di0wrxFSzEOGthYiPrkpv2 J0=; b=lp9/Uom+yj6FAVTAy0R2d1JZWcDUsbaiilh1AsAqLhLJRfUeGwuNxvnvY j196StzksrndYtABeMpMwMXiZVW1+lVCPz+Yv4/uX4/jhcLS+9l9aRlwviCWBD6v Mkdpj1bGURkpUOJAtGCc+uwCwhljY0zQWZ4G3VOVzWvIew2cJ0zk7nPPiWuNt/si pYCvWd5P88jgHn2voWgi/EdEmdcb4nIoZm7uAUcviWC+QeX1/zS/4UGFWii62btq SreOIMesoju6oidbjeQ1NYGpYBkh2+snu18kzxkZuuy31yILWcWEpcVhtBOZlPKN av1d1+MPGBJGpNm5QRdNUtHsBMYYw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudehledgieelucetufdoteggodetrfdotf 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 06CC03280063; Fri, 27 Mar 2020 11:06:23 -0400 (EDT) From: Thomas Monjalon To: Tom Barbette Cc: dev@dpdk.org, Matthew Hall Date: Fri, 27 Mar 2020 16:06:22 +0100 Message-ID: <2812875.WAvfycf1tz@xps> In-Reply-To: <24030728-aa1c-d075-d644-c1f7dc7122b5@kth.se> References: <2838010.xgJ6IN8ObU@xps> <24030728-aa1c-d075-d644-c1f7dc7122b5@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 15:24, Tom Barbette: >=20 > Le 27/03/2020 =E0 14:55, Thomas Monjalon a =E9crit : > > 27/03/2020 13:35, Tom Barbette: > >> Le 27/03/2020 =E0 11:35, Thomas Monjalon a =E9crit : > >>> 27/03/2020 10:14, Tom Barbette: > >>>> CC'ing original participants as I don't see a way out of this. > >>>> > >>>> Le 12/03/2020 =E0 13:04, Tom Barbette a =E9crit : > >>>>> Hi all, > >>>>> > >>>>> If the user follows the quick guide > >>>>> (http://core.dpdk.org/doc/quick-start/) DPDK will be compiled in the > >>>>> "build" folder. > >>>>> > >>>>> However, external applications will always fail to build because > >>>>> RTE_SDK_BIN is strictly defined as $RTE_SDK/$RTE_TARGET, and > >>>>> mk/internal/rte.extvars.mk needs to find .config in $RTE_SDK_BIN. > >>>>> > >>>>> Therefore please apply the patch at: > >>>>> http://patchwork.dpdk.org/patch/9991/ that allows external apps to > >>>>> override $RTE_SDK_BIN. > >>>>> > >>>>> Or (less preferable) modify the quick start guide to use something = more > >>>>> standard that allows to build with external apps (eg use the menu or > >>>>> propose "make config T=3Dx86_64-native-linuxapp-gcc > >>>>> O=3Dx86_64-native-linuxapp-gcc" instead). It's much easier for exte= rnal > >>>>> apps maintainer to refer to the DPDK tutorial for DPDK installation. > >>> > >>> I don't understand the issue. > >>> First 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-l= inux-gcc make -C myapp > >>> > >>> Please can you confirm it works? > >>> > >>> > >> > >> I don't think it is usual to link against an "installed" DPDK, actuall= y. > >> I've only seen people explaining "build DPDK with 1 & 2", which is > >> probably why the quick start also use only that and the usertools menu > >> also only builds in the usual folder SDK/TARGET. > >> > >> Then also using the install method you propose, I'm missing a few > >> libraries, eg -lethdev which I would have to find using > >> -L$RTE_SDK/../../lib which does not sound great. But adding a link to > >> ../../lib under share fixes the problem, and the install script could = do it. > >=20 > > Why are you trying to link a library in RTE_SDK? > > You should set the installed library directory with LD_LIBRARY_PATH. >=20 > I don't want DPDK to be installed system-wide. I have a lot of versions,= =20 > modified for different projects from different people, that has=20 > different compatibility level. And even, different versions compiled for= =20 > different CPU architectures among our cluster. >=20 > I prefer to only rely $RTE_SDK to know where "everything is". I could=20 > tell to my users to add something in their LD_LIBRARY_PATH, but I would=20 > prefer to stick to only the standard RTE_SDK and RTE_TARGET. You can install inside RTE_SDK. This is what the command I gave you to test do. Installation is just organizing files in a directory so it can be consumed. Did you read the commands I sent? It is installing in $(pwd)/myinstall. After install, RTE_SDK becomes $(pwd)/myinstall/share/dpdk. > >> Making RTE_SDK_BIN a ?=3D instead of a :=3D would allow us to fix the > >> non-installed, but built-in-a-funny-folder installation path easily. > >> > >> So I would recommend doing the lib link, but still the change proposed > >> because I'm really not sure people "install" DPDK... > >=20 > > The correct method is installing the library and using standard environ= ment variables. > > The only change I am OK to do is improving the documentation. >=20 > You know best... I still think make install is unnecessary in most cases= =20 > so I would not change the doc either... I say "make install" is a must and there is no reason no to do it. Please check the steps I wrote for you.