From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) by dpdk.org (Postfix) with ESMTP id 0464E95AB for ; Wed, 27 Jan 2016 14:39:39 +0100 (CET) Received: by mail-wm0-f47.google.com with SMTP id l66so3028190wml.0 for ; Wed, 27 Jan 2016 05:39:39 -0800 (PST) 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:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :content-type; bh=ERmAUph9sBcfwNDaObJBZMyR/ecwZ7JAo+yO2r5BLX0=; b=QKIvbdPwdPf2OtIOol++Xakd6zwzcmaLiKE4AoKv1aR5M94C10hRpUxE1qg8jvMT0j g3FSwvz6Zu2tNEUCKtOnZpQsl0s4KpnS6SZAbezuHKSM/7xigTCmsdmvxwtyQTnyNlZb CTIF6yyQULi0L69HZuBAHueAOUBcoyNlpU8dz+QO+E+U7BIjAF2AXisyvFesWJFSjsIY xFlF+S1O9Zq7oGfEw6es1c5B7ig3Hdy89MlOpWzIVc3+X3tspu5KUQpA7KECr03dLJLQ xAXh+me9wdJev9JvNATbwvBkmpW2htpllHc3C/rICEr4PoYwbJk4SOREplhqhRyVsjPu hXaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=ERmAUph9sBcfwNDaObJBZMyR/ecwZ7JAo+yO2r5BLX0=; b=Xc236gus17xCgp27IZzpqTPpNz8wcopgJ7foRwOumfLz5/pOTJDVLSIdo5WHADOUui 76z1FwRmr6ksagwIG/b4vx1MNF04ALMdIb7DCZJmDj1x0FEqq+zcoShKUAMkjA5djuf0 1JhYxuQeYuF5obGfb056+D3oYTv6Tdj0feopvPZdWodva9ocvVzx7XL7SMhg9JOF1v7J kkkKuapsYKDd5jsMqyJCUQPCRXPMnFBuNcfAYPbNRACS9b42ghjBvYBPTaBqBLgUtY0U iYN2AE8DrDmZtRm9uC5qPMgFpxOkssBvTtnfTeSmZ7HRgaThQVuBK2jO7RAI8KKZ3uh6 EjEA== X-Gm-Message-State: AG10YOQXn7yHkVvy3fDU6Erb5jzRfsgxEyTYWRpS5YNpe7uu6GRB7b03gtv8vJvo2y8hgTmT X-Received: by 10.28.142.8 with SMTP id q8mr29930014wmd.47.1453901978841; Wed, 27 Jan 2016 05:39:38 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id ha9sm6305275wjc.3.2016.01.27.05.39.37 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Jan 2016 05:39:38 -0800 (PST) From: Thomas Monjalon To: Matthew Hall Date: Wed, 27 Jan 2016 14:38:29 +0100 Message-ID: <1907511.MEp49p1vlo@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <56A0696A.8090506@mhcomputing.net> References: <1453267824-2880-1-git-send-email-mhall@mhcomputing.net> <2864842.XzLbtfflbQ@xps13> <56A0696A.8090506@mhcomputing.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] rte.extvars.mk: allow overriding RTE_SDK_BIN from the environment X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2016 13:39:39 -0000 2016-01-20 21:15, Matthew Hall: > On 1/20/16 7:27 AM, Thomas Monjalon wrote: > > Hi Matthew, > > > > RTE_SDK_BIN is an internal variable and should not be overriden. > > > > Have you installed DPDK somewhere? Example: > > make install O=mybuild DESTDIR=mylocalinstall > > > > Then you should build your app like this: > > make RTE_SDK=$(readlink -e ../dpdk/mylocalinstall/usr/local/share/dpdk) > > Hello Thomas, > > Is the way the make install target really works documented somewhere? It is poorly described here: http://dpdk.org/doc/guides/prog_guide/dev_kit_root_make_help.html#install-targets > This target did not exist when I first used DPDK in 2011, and since then > I saw various documentation on building DPDK in various places, but not > that much explanation what make install actually does. I recall various > list threads about changing its behavior as well. Historically, "make install" was a convenient default build (with T= option). The DESTDIR option was added to make a real install after building. The standard form (without T=) is now implemented to do a real install. > For example, if I look at this apparently most official document: > > http://dpdk.org/doc/guides/linux_gsg/build_dpdk.html > > It has build examples such as: > > make install T=x86_64-native-linuxapp-gcc This command finishes with this message: Installation cannot run with T defined and DESTDIR undefined Yes you are right, some docs are neither complete nor up-to-date. Volunteers are welcome. > But it does not discuss "O=" or "DESTDIR=" or any other additional > options. From some experiments on my machine, it looks like maybe I > could do this: > > make install "T=${RTE_TARGET}" "O=build" "DESTDIR=build" > > Is that a valid possibility, to keep it all in one easy directory? Yes you can install where you want. Note that this command (with T= and O=) will build in the directory $O/$T i.e. build/${RTE_TARGET} and install in build/ Please confirm that this patch is not needed. Thanks