From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH] mk: fix kernel modules build dependency Date: Thu, 29 Mar 2018 17:38:23 +0100 Message-ID: <1b87dc99-c4a5-21d0-9d78-3ea024f6a0c4@intel.com> References: <20180329153931.26351-1-thomas@monjalon.net> <0b1a7c34-1dd0-b47b-5ee7-7ea3f1ec4308@intel.com> <1556410.U3gqVypkhP@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: hemant.agrawal@nxp.com, dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id B7E2F2C5E for ; Thu, 29 Mar 2018 18:38:27 +0200 (CEST) In-Reply-To: <1556410.U3gqVypkhP@xps> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 3/29/2018 5:32 PM, Thomas Monjalon wrote: > 29/03/2018 17:48, Ferruh Yigit: >> On 3/29/2018 4:39 PM, Thomas Monjalon wrote: >>> Some kernel modules may need some header files to be "installed" >>> in the build directory. >>> >>> When running multiple threads of make, kernel modules can try to >>> be compiled before the lib headers are ready: >>> make -j3 >>> kernel/linux/kni/kni_misc.c:19:37: fatal error: >>> exec-env/rte_kni_common.h: No such file or directory >> >> Is there a reason to keep header in eal when module itself moved into kernel? > > It seems you missed my comment below: > > On a related note, this header file > lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h > could be moved to lib/librte_kni/ > Opinion? Ahh, yes we are saying same thing. But not sure if it should go under lib/librte_kni/ or kernel/linux/kni/? I lean to kernel/linux/kni/.