From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] net/virtio: build is broken on FreeBSD
Date: Wed, 18 Jan 2017 03:08:58 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E36511179AD@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <6199672.AS3ZBII79S@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, January 18, 2017 6:10 AM
> To: Andrew Rybchenko; Yuanhan Liu; Tan, Jianfeng
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] net/virtio: build is broken on FreeBSD
>
> 2017-01-17 17:39, Andrew Rybchenko:
> > dpdk-next-net build is broken for me on FreeBSD 10.3 and 11.0 regardless
> > clang/gcc:
>
> Thanks for reporting.
>
> It is due to the pull of next-virtio tree.
> It is broken also on Linux when virtio-user is disabled.
Thank you Andrew for reporting! And I see Thomas's patch have fixed this problem. I tested latest code on Freebsd 10.2, it can be compiled now.
Thank you Thomas.
>
> Unfortunately the compilation test in CI failed to apply the patch:
> http://dpdk.org/dev/patchwork/patch/19352/
Is this still a problem?
Thanks,
Jianfeng
prev parent reply other threads:[~2017-01-18 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 14:39 Andrew Rybchenko
2017-01-17 22:09 ` Thomas Monjalon
2017-01-17 22:22 ` [dpdk-dev] [PATCH] net/virtio: fix build without virtio-user Thomas Monjalon
2017-01-18 2:42 ` Yuanhan Liu
2017-01-18 3:08 ` Tan, Jianfeng [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=ED26CBA2FAD1BF48A8719AEF02201E36511179AD@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yuanhan.liu@linux.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).