From: spyroot <spyroot@gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] KNI compilation
Date: Mon, 30 Aug 2021 22:41:00 +0400 [thread overview]
Message-ID: <CABsV3rANDX1yBSnCOmJ5GwWbTsm2tBxGkvBt1VerC70T-tpo-A@mail.gmail.com> (raw)
In-Reply-To: <5bc2db4b-0cf8-d474-281c-551213c25532@intel.com>
Hi Ferruh,
Sorry, I forgot to mention, Yes, I was compiling with -Denable_kmods=true.
I just partially found a root cause. The target system Photon OS (It
VMware distro)
It has 4 kernels variation regular, RT, ESX, security. ( I was using ESX
variation that optimized for
ESXi but it looks like something is disabled in the kernel that prevents
KNI to compile) when
I use a regular kernel source tree, it does compile.
I was trying to figure out what KNI actually requires from the kernel
source tree or what instrumentation
I can use it to see the more verbose errors. ninja -v doesn't really
provide details.
Thank you very much
On Mon, Aug 30, 2021 at 9:44 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 8/30/2021 5:47 PM, spyroot wrote:
> > Hi Folks,
> >
> > I troubleshooting already for a couple of hours but still not clear why
> > exactly the build process
> > failing on the KNI module. I've tried to disable KNI but it same issue.
> > Any ideas what might be a root cause. It x86_64
> >
> >
> > [1/2] Generating rte_kni with a custom command
> > FAILED: kernel/linux/kni/rte_kni.ko
> > make -j4 -C /lib/modules/5.10.52-3.ph4-esx/build
> > M=/root/dpdk-stable-20.11.2/build/kernel/linux/kni
> > src=/root/dpdk-stable-20.11.2/kernel/linux/kni 'MODULE_CFLAGS=-include
> > /root/dpdk-stable-20.11.2/config/rte_config.h
> > -I/root/dpdk-stable-20.11.2/lib/librte_eal/include
> > -I/root/dpdk-stable-20.11.2/lib/librte_kni
> > -I/root/dpdk-stable-20.11.2/build
> > -I/root/dpdk-stable-20.11.2/kernel/linux/kni' modules
> > make: Entering directory '/usr/src/linux-headers-5.10.52-3.ph4-esx'
> > make[1]: *** No rule to make target
> > '/root/dpdk-stable-20.11.2/build/kernel/linux/kni/kni_misc.o', needed by
> > '/root/dpdk-stable-20.11.2/build/kernel/linux/kni/rte_kni.o'. Stop.
> > make: *** [Makefile:1821:
> /root/dpdk-stable-20.11.2/build/kernel/linux/kni]
> > Error 2
> > make: Leaving directory '/usr/src/linux-headers-5.10.52-3.ph4-esx'
> > ninja: build stopped: subcommand failed.
> >
> > Kind Regards,
> > Mus>
> >
>
> Hi spyroot (Mus> ?),
>
> modules already disabled by default, you should be enabling it via
> '-Denable_kmods=true' meson option, if you want to disable kni just not
> enabling
> kmods should be enough.
>
> btw, I have tried and not able to reproduce the issue in 20.11.2 in my
> platforml, kni compiles fine.
> Can you confirm you have kernel source installed in your system?
> Or to be more specific, does '/usr/src/linux-headers-5.10.52-3.ph4-esx'
> patch
> has kernel source code?
>
> And can you please share your full commands for build?
>
> Cheers,
> ferruh
>
prev parent reply other threads:[~2021-08-30 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 16:47 spyroot
2021-08-30 17:44 ` Ferruh Yigit
2021-08-30 18:41 ` spyroot [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=CABsV3rANDX1yBSnCOmJ5GwWbTsm2tBxGkvBt1VerC70T-tpo-A@mail.gmail.com \
--to=spyroot@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).