DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Shreyansh Jain <shreyansh.jain@nxp.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Herbert Guan <Herbert.Guan@arm.com>,
	"Bhagavatula, Pavan" <Pavan.Bhagavatula@cavium.com>
Subject: Re: [dpdk-dev] meson support : cross compile issues
Date: Wed, 28 Feb 2018 05:16:02 +0000	[thread overview]
Message-ID: <AM2PR04MB075301E436FA254E98FDE72D89C70@AM2PR04MB0753.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20180227145211.GA10664@bricha3-MOBL3.ger.corp.intel.com>

Hi Bruce,

> 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)

[Hemant]  setting kernel_dir in meson_options.txt worked for me.
> 
> >
> > 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://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgcc.gn
> u.org%2Fonlinedocs%2Fgcc%2FWarning-
> Options.html&data=02%7C01%7Chemant.agrawal%40nxp.com%7Cbe391f8ced
> e54b43679808d57df1b4e4%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C
> 1%7C636553399436715184&sdata=u3wSqw8DJ6dROat%2B%2BUr2EeusPmv90Z
> GPYRvitUuWIHE%3D&reserved=0
> "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"

[Hemant]  Thanks it helps.

> 
> 
> > ../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

      reply	other threads:[~2018-02-28  5:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 14:38 Hemant Agrawal
2018-02-27 14:52 ` Bruce Richardson
2018-02-28  5:16   ` Hemant Agrawal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM2PR04MB075301E436FA254E98FDE72D89C70@AM2PR04MB0753.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=Herbert.Guan@arm.com \
    --cc=Pavan.Bhagavatula@cavium.com \
    --cc=akhil.goyal@nxp.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=shreyansh.jain@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).