DPDK usage discussions
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
To: 宋捷 <songj@zctt.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] 答?:  igb_uio.ko is not generated via make/dpdk-setup.sh
Date: Fri, 17 Apr 2020 17:02:16 +0900	[thread overview]
Message-ID: <20200417170216.54A2.17218CA3@ntt-tx.co.jp_1> (raw)
In-Reply-To: <0D293C5FA1DB70FF@nttdocomo.co.jp>

Hello Songi,

Thanks for your checking the issue.

I think that considering that two person encountered the same issue,
it looks that it is not coincident.
It is highly possible that there is some problem with building "make"
system.

If I deeply look into make file, I can fix my problem.
But I am not good at looking/analyzing make file.

So DPDK experts,
I need, we need some explanation or fix for this isssue!

Thanks for your help.

BR,
Hideyuki Yamashita
NTT TechnoCross

> I get the same issue」ャ
> I build DPDK 20.02 with "make install T=x86_64-native-linuxapp-gcc", there
> is not kmod folder under x86_64-native-linuxapp-gcc. 
> So I have to copy kmod from dpdk-stable-19.11.1 into DPDK 20.02, the igb_uio
> source code is same between these two version.
> 
> 
> 
> 
> -----モハシ?ヤュシ?-----
> キ「シ?ネヒ: users [mailto:users-bounces@dpdk.org] エ〓\xF9\x01Hideyuki Yamashita
> キ「ヒヘハアシ

  parent reply	other threads:[~2020-04-17  8:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  6:36 [dpdk-users] " Hideyuki Yamashita
2020-04-17  6:17 ` Hideyuki Yamashita
2020-04-17  7:51   ` [dpdk-users] 答复: " 宋捷
     [not found]   ` <0D293C5FA1DB70FF@nttdocomo.co.jp>
2020-04-17  8:02     ` Hideyuki Yamashita [this message]
2020-04-17  8:59       ` [dpdk-users] 答?: " Trahe, Fiona
2020-04-20 10:02         ` Hideyuki Yamashita
2020-04-20 12:23           ` Trahe, Fiona

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=20200417170216.54A2.17218CA3@ntt-tx.co.jp_1 \
    --to=yamashita.hideyuki@ntt-tx.co.jp \
    --cc=songj@zctt.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).