From: "xu,huilong" <huilongx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,huilong" <huilongx.xu@intel.com>
Subject: [dts] [PATCH V1] fix dpdk compile error
Date: Thu, 8 Sep 2016 09:36:40 +0800 [thread overview]
Message-ID: <1473298600-6652-1-git-send-email-huilongx.xu@intel.com> (raw)
dpdk makefile add a new function for build resource file.
so before compile dpdk again, we need remove the resource.
Signed-off-by: xu,huilong <huilongx.xu@intel.com>
---
framework/project_dpdk.py | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/framework/project_dpdk.py b/framework/project_dpdk.py
index 4e44793..803585d 100644
--- a/framework/project_dpdk.py
+++ b/framework/project_dpdk.py
@@ -170,6 +170,7 @@ class DPDKdut(Dut):
build_time = 900
# clean all
self.send_expect("rm -rf " + target, "#")
+ self.send_expect("rm -rf %s" % r'./app/test/test_resource_c.res.o' , "#")
# compile
out = self.send_expect("make -j install T=%s %s" % (target, extra_options), "# ", build_time)
@@ -188,6 +189,7 @@ class DPDKdut(Dut):
"""
# clean all
self.send_expect("rm -rf " + target, "#")
+ self.send_expect("rm -rf %s" % r'./app/test/test_resource_c.res.o' , "#")
# compile
out = self.send_expect("make -j %d install T=%s CC=gcc48" % (self.number_of_cores,
@@ -312,6 +314,7 @@ class DPDKdut(Dut):
"""
Build dpdk sample applications on linux.
"""
+ self.send_expect("rm -rf %s" % r'./app/test/test_resource_c.res.o' , "#")
return self.send_expect("make -j -C %s %s" % (folder, extra_options),
"# ", 90)
@@ -319,6 +322,7 @@ class DPDKdut(Dut):
"""
Build dpdk sample applications on Freebsd.
"""
+ self.send_expect("rm -rf %s" % r'./app/test/test_resource_c.res.o' , "#")
return self.send_expect("make -j -C %s %s CC=gcc48" % (folder, extra_options),
"# ", 90)
--
1.9.3
next reply other threads:[~2016-09-08 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 1:36 xu,huilong [this message]
2016-09-08 6:38 ` Liu, Yong
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=1473298600-6652-1-git-send-email-huilongx.xu@intel.com \
--to=huilongx.xu@intel.com \
--cc=dts@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).