All of lore.kernel.org
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: <jerinj@marvell.com>, <dev@dpdk.org>,
	Jan Viktorin <viktorin@rehivetech.com>,
	Ruifeng Wang <ruifeng.wang@arm.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	Stanislaw Kardach <kda@semihalf.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>,
	<juraj.linkes@pantheon.tech>
Subject: Re: [dpdk-dev] [PATCH v2] build: ccache support for cross build
Date: Thu, 9 Jun 2022 09:44:25 +0800	[thread overview]
Message-ID: <54dfdab9-e93f-cdcf-0296-bacaf500d2f2@huawei.com> (raw)
In-Reply-To: <20220608171304.945454-1-jerinj@marvell.com>

Test with: arm64_kunpeng920/930 and gcc-7/10, also with ccache or no, all pass

Acked-by: Chengwen Feng <fengchengwen@huawei.com>


On 2022/6/9 1:13, jerinj@marvell.com wrote:
> From: Jerin Jacob <jerinj@marvell.com>
> 
> By default, ccache is not used for cross build[1].
> Update all cross files to use ccache if it is available
> in build machine.
> 
> Also, updated devtools/test-meson-builds.sh
> script to find the correct DPDK_TARGET due to
> change in cross file syntax.
> 
> [1]
> https://mesonbuild.com/Machine-files.html
> 
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> 
> v2:
> - Rebased with master, therefore added update riscv64 cross files
> - Fixed DPDK_TARGET detection with devtools/test-meson-builds.sh 
> due to cross file synatx update.
> 
>  config/arm/arm32_armv8_linux_gcc           | 4 ++--
>  config/arm/arm64_armada_linux_gcc          | 4 ++--
>  config/arm/arm64_armv8_linux_clang_ubuntu  | 4 ++--
>  config/arm/arm64_armv8_linux_gcc           | 4 ++--
>  config/arm/arm64_bluefield_linux_gcc       | 4 ++--
>  config/arm/arm64_centriq2400_linux_gcc     | 4 ++--
>  config/arm/arm64_cn10k_linux_gcc           | 4 ++--
>  config/arm/arm64_cn9k_linux_gcc            | 4 ++--
>  config/arm/arm64_dpaa_linux_gcc            | 4 ++--
>  config/arm/arm64_emag_linux_gcc            | 4 ++--
>  config/arm/arm64_graviton2_linux_gcc       | 4 ++--
>  config/arm/arm64_kunpeng920_linux_gcc      | 4 ++--
>  config/arm/arm64_kunpeng930_linux_gcc      | 4 ++--

[snip]

> 


  reply	other threads:[~2022-06-09  1:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  9:23 [dpdk-dev] [PATCH v1] build: ccache support for cross build jerinj
2022-06-02  9:41 ` Bruce Richardson
2022-06-02  9:43   ` Jerin Jacob
2022-06-02 10:55     ` Thomas Monjalon
2022-06-02 12:00       ` Jerin Jacob
2022-06-02 13:33         ` Bruce Richardson
2022-06-08  8:22         ` Jerin Jacob
2022-06-08  8:30           ` Thomas Monjalon
2022-06-08 17:16             ` Jerin Jacob
2022-06-08 18:30               ` Stanisław Kardach
2022-06-08 17:13 ` [dpdk-dev] [PATCH v2] " jerinj
2022-06-09  1:44   ` fengchengwen [this message]
2022-06-10  7:30   ` Ruifeng Wang
2022-06-14 16:09     ` Thomas Monjalon
2022-06-14 16:01   ` Thomas Monjalon

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=54dfdab9-e93f-cdcf-0296-bacaf500d2f2@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=jerinj@marvell.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=kda@semihalf.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=ruifeng.wang@arm.com \
    --cc=thomas@monjalon.net \
    --cc=viktorin@rehivetech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.