From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Cao, Waterman" <waterman.cao@intel.com>
Cc: DPDK_SW_ENG <dpdk_sw_eng@intel.com>,
"Wang, Limin" <limin.wang@intel.com>,
"Tang, HaifengX" <haifengx.tang@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>,
"Qiu, Michael" <michael.qiu@intel.com>,
"Zhang, XiaopengX" <xiaopengx.zhang@intel.com>,
qabuild <qabuild@intel.com>, "Xie, Huawei" <huawei.xie@intel.com>,
"Guan, JunchunX" <junchunx.guan@intel.com>
Subject: Re: [dpdk-test-report] [update[: DPDK OS Building Test Report
Date: Fri, 11 Dec 2015 02:47:42 +0100 [thread overview]
Message-ID: <16674701.xCQvrH3D4N@xps13> (raw)
In-Reply-To: <AA3F441F262C58498CD6D0C1801DE7EB0AFEF240@SHSMSX103.ccr.corp.intel.com>
2015-12-11 01:43, Cao, Waterman:
> Hi All,
>
> Till now, there are only 3 major building errors in DPDK example
And there are some errors due to VM configuration.
Example: libvirt.h missing. Is it possible to fix it please?
> 1. netmap_compact example has compilation errors in SUSE11SP3 and SUSE11SP2
> Till now, we don’t have owner for netmap_compact example ， Linux Kernel is 3.0.13-0 and GCC is 4.5.1
>
> Does anybody familiar with this example app?
>
> 2. pipeline example in RHEL65_64 / CENTOS65_64 ,
>
> As I knew, Roy Fan and packet Framework developers already submitted patch to fix #2
It has been applied (5c25894) but the error is still there.
> 3. vHost Example in RHEL65_64 / RHEL70_64
>
> Huawei will investigate #3 , see if how to fix it.
prev parent reply other threads:[~2015-12-11 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 1:43 Cao, Waterman
2015-12-11 1:47 ` Thomas Monjalon [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=16674701.xCQvrH3D4N@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dpdk_sw_eng@intel.com \
--cc=haifengx.tang@intel.com \
--cc=huawei.xie@intel.com \
--cc=junchunx.guan@intel.com \
--cc=limin.wang@intel.com \
--cc=michael.qiu@intel.com \
--cc=qabuild@intel.com \
--cc=test-report@dpdk.org \
--cc=waterman.cao@intel.com \
--cc=xiaopengx.zhang@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).