test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Chen, BoX C" <box.c.chen@intel.com>
To: "Wu, ChangqingX" <changqingx.wu@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] framework/delete specify compiler gcc48
Date: Mon, 16 Sep 2019 09:49:00 +0000	[thread overview]
Message-ID: <F9D0342A3C124046BB4E6A739EEFDEFE0E3F9643@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1568601438-1289-1-git-send-email-changqingx.wu@intel.com>

Tested-by:  Chen, BoX C <box.c.chen@intel.com>


> -----Original Message-----
> From: Wu, ChangqingX
> Sent: September 16, 2019 10:37
> To: dts@dpdk.org
> Cc: Chen, BoX C <box.c.chen@intel.com>; Wu, ChangqingX
> <changqingx.wu@intel.com>
> Subject: [dts][PATCH V1] framework/delete specify compiler gcc48
> 
> do not need specify the gcc48 when compiling dpdk or app with clang on
> freebsd, otherwise will get compile error
> 
> Signed-off-by: changqingxwu <changqingx.wu@intel.com>
> ---
>  framework/project_dpdk.py | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/framework/project_dpdk.py b/framework/project_dpdk.py
> index f75a4b9..ddad526 100644
> --- a/framework/project_dpdk.py
> +++ b/framework/project_dpdk.py
> @@ -243,15 +243,15 @@ class DPDKdut(Dut):
>          self.send_expect("rm -rf %s" % r'./app/test/test_resource_c.res.o' , "#")
>          self.send_expect("rm -rf %s" % r'./app/test/test_resource_tar.res.o' ,
> "#")
>          self.send_expect("rm -rf %s" % r'./app/test/test_pci_sysfs.res.o' , "#")
> -        build_time = 120
> +        build_time = 180
>          # compile
> -        out = self.send_expect("make -j %d install T=%s CC=gcc48" %
> (self.number_of_cores,
> +        out = self.send_expect("make -j %d install T=%s" %
> + (self.number_of_cores,
>                                                                       target),
>                                 "#", build_time)
>          if("Error" in out or "No rule to make" in out):
>              self.logger.error("ERROR - try without '-j'")
>              # if Error try to execute make without -j option
> -            out = self.send_expect("make install T=%s CC=gcc48" % target,
> +            out = self.send_expect("make install T=%s" % target,
>                                     "#", build_time)
> 
>          assert ("Error" not in out), "Compilation error..."
> @@ -386,7 +386,7 @@ class DPDKdut(Dut):
>          self.send_expect("rm -rf %s" % r'./app/test/test_resource_c.res.o' , "#")
>          self.send_expect("rm -rf %s" % r'./app/test/test_resource_tar.res.o' ,
> "#")
>          self.send_expect("rm -rf %s" % r'./app/test/test_pci_sysfs.res.o' , "#")
> -        return self.send_expect("make -j %d -C %s %s CC=gcc48" %
> (self.number_of_cores,
> +        return self.send_expect("make -j %d -C %s %s" %
> + (self.number_of_cores,
>                                                                    folder, extra_options),
>                                  "# ", 180)
> 
> --
> 2.17.2


  reply	other threads:[~2019-09-16  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16  2:37 changqingxwu
2019-09-16  9:49 ` Chen, BoX C [this message]
2019-09-18 10:50 ` Tu, Lijuan

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=F9D0342A3C124046BB4E6A739EEFDEFE0E3F9643@shsmsx102.ccr.corp.intel.com \
    --to=box.c.chen@intel.com \
    --cc=changqingx.wu@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).