From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v6 0/4] Hyper-V netvsc PMD and VMBus support
Date: Sun, 13 May 2018 00:02:59 +0200 [thread overview]
Message-ID: <9311220.sRLYH6gzLP@xps> (raw)
In-Reply-To: <f1fe4272-c970-7164-1709-8af788238fe4@intel.com>
11/05/2018 18:50, Ferruh Yigit:
> On 5/9/2018 1:26 AM, Stephen Hemminger wrote:
> > Stephen Hemminger (4):
> > bus/vmbus: add hyper-v virtual bus support
> > net/netvsc: add hyper-v netvsc network device
> > net/netvsc: add documentation
> > bus/vmbus and net/netvsc: add meson build support
>
> I confirm my test scripts passes for x86, not able to cross build for other
> architectures because of uuid dependency and I am missing cross version of it.
> note: need to enable both LIBRTE_VMBUS & NETVSC_PMD
Unfortunately, I have a compilation error with meson because of uuid dependency:
Library uuid found: NO
[...]
./drivers/bus/vmbus/rte_bus_vmbus.h:23:10: fatal error: uuid/uuid.h:
No such file or directory
I think it is missing a "build = false" when dep is not found.
In the next revision, please merge meson files in first patches, thanks.
next prev parent reply other threads:[~2018-05-12 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 0:26 Stephen Hemminger
2018-05-09 0:26 ` [dpdk-dev] [PATCH v6 1/4] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-05-09 0:26 ` [dpdk-dev] [PATCH v6 2/4] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-05-09 0:26 ` [dpdk-dev] [PATCH v6 3/4] net/netvsc: add documentation Stephen Hemminger
2018-05-09 15:57 ` Kovacevic, Marko
2018-05-09 0:26 ` [dpdk-dev] [PATCH v4 4/4] bus/vmbus and net/netvsc: add meson build support Stephen Hemminger
2018-05-11 16:50 ` [dpdk-dev] [PATCH v6 0/4] Hyper-V netvsc PMD and VMBus support Ferruh Yigit
2018-05-11 17:38 ` Stephen Hemminger
2018-05-12 22:02 ` Thomas Monjalon [this message]
2018-05-13 17:22 ` Stephen Hemminger
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=9311220.sRLYH6gzLP@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.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).