DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Joakim Zhang <qiangqing.zhang@nxp.com>,
	"users@dpdk.org" <users@dpdk.org>,  "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Build KNI module failed
Date: Fri, 30 Apr 2021 13:54:14 +0000	[thread overview]
Message-ID: <0933a03b97e14482bd0425c59f52d8b1@pantheon.tech> (raw)
In-Reply-To: <DB8PR04MB6795133FB56F7791CD7A4F39E6419@DB8PR04MB6795.eurprd04.prod.outlook.com>

Maybe we actually need to step back a bit and talk about versions.

Which DPDK version are you using?
Why are you using the old make build system instead of Meson?

Support for KNI cross-compilation was only added recently to Meson and I don't know enough about the old Make system to comment on that.

Juraj

> -----Original Message-----
> From: Juraj Linkeš
> Sent: Friday, April 30, 2021 2:18 PM
> To: 'Joakim Zhang' <qiangqing.zhang@nxp.com>; users@dpdk.org;
> dev@dpdk.org
> Subject: RE: Build KNI module failed
> 
> Hi Joakim,
> 
> When I cross-compiled KNI I only used gcc that comes with Ubuntu, e.g.:
> sudo apt install gcc-aarch64-linux-gnu libc6-dev-arm64-cross pkg-config-
> aarch64-linux-gnu
> 
> Which Ubuntu version are you using? The Ubuntu18.04 gcc works fine:
> aarch64-linux-gnu-gcc -v
> gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)
> 
> This is a bit strange, since the versions are the same/similar.
> 
> I am using this meson invocation:
> meson kni-cross-gcc -Denable_kmods=true -Dkernel_dir=/home/jlinkes/linux --
> cross-file config/arm/arm64_armv8_linux_gcc
> 
> /home/jlinkes/linux is where I have my Linux git repo.
> 
> Juraj
> 
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Joakim Zhang
> > Sent: Tuesday, April 27, 2021 11:43 AM
> > To: users@dpdk.org; dev@dpdk.org
> > Subject: [dpdk-dev] Build KNI module failed
> >
> >
> > Hi guys,
> >
> > Is there anyone met gcc build error when build KNI module on Ubuntu to
> > cross build ARM64?
> > I tried both gcc-linaro-6.5.0-2018.12-x86_64_aarch64-linux-gnu and
> > gcc-linaro- 7.5.0-2019.12-x86_64_aarch64-linux-gnu.
> >
> > The error log as below, any comments would be appreciated! Thanks a lot!
> > == Build kernel/linux/kni
> >   CC [M]  /home/zqq/dpdk/arm64-dpaa-linuxapp-
> > gcc/build/kernel/linux/kni/kni_misc.o
> > aarch64-linux-gnu-gcc: error: unrecognized command line option
> > '-mstack- protector-guard=sysreg'; did you mean '-fstack-protector-strong'?
> > aarch64-linux-gnu-gcc: error: unrecognized command line option
> > '-mstack- protector-guard-reg=sp_el0'; did you mean '-fstack-protector-all'?
> > aarch64-linux-gnu-gcc: error: unrecognized command line option
> > '-mstack- protector-guard-offset=1096'; did you mean '-fstack-protector-
> strong'?
> > scripts/Makefile.build:279: recipe for target
> > '/home/zqq/dpdk/arm64-dpaa-
> > linuxapp-gcc/build/kernel/linux/kni/kni_misc.o' failed
> >
> > I search the source code, have not found these gcc command line options.
> >
> > Best Regards,
> > Joakim Zhang
> >



  parent reply	other threads:[~2021-04-30 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27  9:42 Joakim Zhang
2021-04-30 12:17 ` Juraj Linkeš
2021-04-30 13:54 ` Juraj Linkeš [this message]
2021-05-06  5:17   ` Joakim Zhang

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=0933a03b97e14482bd0425c59f52d8b1@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=dev@dpdk.org \
    --cc=qiangqing.zhang@nxp.com \
    --cc=users@dpdk.org \
    /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).