From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 4E4241B682; Wed, 31 Jan 2018 00:44:42 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D582E211D9; Tue, 30 Jan 2018 18:44:41 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 30 Jan 2018 18:44:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ounbPhvhmyAOt9GT/Nm5+ERfuU rjcoyDIaOiQLN94A4=; b=ihIxd/M80IH8Z+1LO8L3dYhUm4bIKO5P2PeDV3OgYT g8U79DCeEh2bfjkrURhY2I86GFGk3Kwbj3ap2K6YvswhvsMICeQqaPMzqtmeN03S ODFg2YE+Dpr9RqbRz6xVzANzAL5AZA561RNVWbKwam5jAPwVPTPXn4dDhHsM2G6d A= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ounbPh vhmyAOt9GT/Nm5+ERfuUrjcoyDIaOiQLN94A4=; b=g4cvh5XGCy0QDLP5czcK0N jEVSuiUtgs7XNHUiYkEaA6sc1EP5l4WPP8EC8dbocYTl8nM6IjBs0uclWURjIB69 bnsS4z9u12Hg1MBy1oeVDGTnijIxcMZyI55xQLdNDvhgbciprduwg2NksLsMk2CB k7pp0LvoAIcoBJJM3fdb86OIp3qTThrjF0HXCmK8N9R6uaGuYJOs2DayNlDp/52W 2CfW20SmA5mmeAHodFcWLMvS06tqDGa2xEL8BlSBiTwYYTOHNO7tzcEGePliDbOr n/xAfzx6aByTLmmX/jr7MaW9Yyeb3LzyyvAiweVtdT7946iHS4S5iwZM6WdfyCqg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 8A13A7E3D5; Tue, 30 Jan 2018 18:44:41 -0500 (EST) From: Thomas Monjalon To: "Kovacevic, Marko" Cc: dev@dpdk.org, "Varghese, Vipin" , "stable@dpdk.org" Date: Wed, 31 Jan 2018 00:43:55 +0100 Message-ID: <2335057.AkUuH7Y4gb@xps> In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D191E4C@BGSMSX101.gar.corp.intel.com> References: <20180122105905.6996-1-marko.kovacevic@intel.com> <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D191E4C@BGSMSX101.gar.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1] mk: support building with renamed makefile 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, 30 Jan 2018 23:44:42 -0000 > > The build system made a recursive call to "make" after creating the build > > directory. This recursive call used the hard-coded filename "Makefile", which > > prevented builds from working if the file was renamed and make called using > > "make -f". Taking the filename from MAKEFILES_LIST make variable fixes this. > > > > Fixes: af75078fece3 ("first public release") > > Cc: stable@dpdk.org > > > > Signed-off-by: Marko Kovacevic > > I have validated on Linux environment with custom make file name as 'Makefile.test'. > > Acked-by: Vipin Varghese Applied, thanks