From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: [PATCH 1/2] build: fix kernel compile on cross-build Date: Wed, 18 Apr 2018 22:05:20 +0100 Message-ID: <20180418210521.277384-2-bruce.richardson@intel.com> References: <20180418210521.277384-1-bruce.richardson@intel.com> Cc: Bruce Richardson To: dev@dpdk.org Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id B06E569D4 for ; Wed, 18 Apr 2018 23:05:28 +0200 (CEST) In-Reply-To: <20180418210521.277384-1-bruce.richardson@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" When cross-compiling, if no kernel_dir was specified, then the kernel modules were still being compiled for the build machine. Fix this by only building modules on cross-compile when we have a kernel_dir value set. Fixes: a52f4574f798 ("igb_uio: build with meson") Signed-off-by: Bruce Richardson --- meson.build | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/meson.build b/meson.build index cc16595cb..9e3b44931 100644 --- a/meson.build +++ b/meson.build @@ -26,10 +26,14 @@ subdir('config') # build libs and drivers subdir('lib') -subdir('kernel') subdir('buildtools') subdir('drivers') +# build kernel modules if we have a kernel path, or we are not cross compiling +if get_option('kernel_dir') != '' or not meson.is_cross_build() + subdir('kernel') +endif + # build binaries and installable tools subdir('usertools') subdir('app') -- 2.14.3