From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 5F81210B7 for ; Tue, 27 Feb 2018 15:52:18 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Feb 2018 06:52:16 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,401,1515484800"; d="scan'208";a="23591400" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.77]) by fmsmga002.fm.intel.com with SMTP; 27 Feb 2018 06:52:14 -0800 Received: by (sSMTP sendmail emulation); Tue, 27 Feb 2018 14:52:13 +0000 Date: Tue, 27 Feb 2018 14:52:11 +0000 From: Bruce Richardson To: Hemant Agrawal Cc: "dev@dpdk.org" , Shreyansh Jain , Akhil Goyal , Herbert Guan , "Bhagavatula, Pavan" Message-ID: <20180227145211.GA10664@bricha3-MOBL3.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.3 (2018-01-21) Subject: Re: [dpdk-dev] meson support : cross compile issues 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, 27 Feb 2018 14:52:18 -0000 On Tue, Feb 27, 2018 at 02:38:53PM +0000, Hemant Agrawal wrote: > Hi, > > How do we set CROSS COMPILE kernel path support. E.g. something equivalent to RTE_KERNELDIR for Makefile > > * Currently the Igb_uio compilation fails. > * Also, there is no check to disable igb_uio compilation by flag e.g. CONFIG_RTE_EAL_IGB_UIO=n > > I have not had time to look at the cross-compilation of kernel modules yet, so patches welcome. :-) However, it should be possible to disable the kernel modules generally using "enable_kmods" option (see meson_options.txt) > > Other minor issue observed is that though the cross compile is set as 6.3, the gcc 7 flags (which is my host compiler version) is getting enabled. Causing following errors: > Actually, this is a gcc quirk. GCC does not report an error for cmdline flags disabling unknown warnings, unless other errors are displayed. This means that when meson tries the options, GCC reports as supporting them. It also means that it's not a problem when you do see them - just fix the other errors and the warnings about the flags will disappear. See: https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html "However, if the -Wno- form is used, the behavior is slightly different: no diagnostic is produced for -Wno-unknown-warning unless other diagnostics are being produced. This allows the use of new -Wno- options with old compilers, but if something goes wrong, the compiler warns that an unrecognized option is present" > ../drivers/bus/dpaa/dpaa_bus.c: At top level: > > cc1: warning: unrecognized command line option ‘-Wno-format-truncation’ > > cc1: warning: unrecognized command line option ‘-Wno-address-of-packed-member’ > > Regards, > Hemant > Regards, /Bruce