DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jack <qiujiangkun@foxmail.com>, dev <dev@dpdk.org>
Cc: Finn Christensen <fc@napatech.com>, Michael Lilja <ml@napatech.com>
Subject: Re: [dpdk-dev] DPDK Compiling Error on New Fedora 32: drivers/net/ntacc/meson.build:31:0: ERROR: Include dir /include does not exist.
Date: Mon, 28 Sep 2020 09:47:44 +0100	[thread overview]
Message-ID: <0efa2b2f-bded-0f71-fc4a-11557e02be4a@intel.com> (raw)
In-Reply-To: <tencent_A1B6008E417950D65E694A325A775729EB08@qq.com>

On 9/25/2020 3:27 PM, Jack wrote:
> Hi,
> Compiling error:
> drivers/net/ntacc/meson.build:31:0: ERROR: Include dir /include does not exist.
> 
> 
> To fix:
> drivers/net/ntacc/meson.build&nbsp;
> 25| PATH = '/usr'
> 
> 
> Sincerely,
> Jack
> 

Hi Jack,

Unfortunately Napatech drivers are not upstreamed, so it is not officially 
supported by project, and we can't help there, it is Napatech's problem to solve.

      reply	other threads:[~2020-09-28  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25 14:27 Jack
2020-09-28  8:47 ` Ferruh Yigit [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=0efa2b2f-bded-0f71-fc4a-11557e02be4a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=fc@napatech.com \
    --cc=ml@napatech.com \
    --cc=qiujiangkun@foxmail.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).