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 16:48:16 +0100 Message-ID: <0b1a7c34-1dd0-b47b-5ee7-7ea3f1ec4308@intel.com> References: <20180329153931.26351-1-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Thomas Monjalon , hemant.agrawal@nxp.com Return-path: Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id C1CA61F28 for ; Thu, 29 Mar 2018 17:48:18 +0200 (CEST) In-Reply-To: <20180329153931.26351-1-thomas@monjalon.net> 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 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?