patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Gavin Hu <gavin.hu@arm.com>
To: dev@dpdk.org
Cc: stable@dpdk.org
Subject: [dpdk-stable] [PATCH v6 4/7] build: fix the meson build warning
Date: Thu, 14 Jun 2018 17:51:24 +0800	[thread overview]
Message-ID: <20180614095127.16245-5-gavin.hu@arm.com> (raw)
In-Reply-To: <20180614095127.16245-1-gavin.hu@arm.com>

This is to fix the unnecessary warning output, it is not consistent with
the configurations of other platforms.

WARNING: Cross file does not specify strip binary, result will not be
stripped.

Fixes: e53a5299d2 ("build: support vendor specific ARM cross builds")
Cc: stable@dpdk.org

Signed-off-by: Gavin Hu <gavin.hu@arm.com>
Reviewed-by: Phil Yang <phil.yang@arm.com>
Reviewed-by: Song Zhu <song.zhu@arm.com>
---
 config/arm/arm64_thunderx_linuxapp_gcc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config/arm/arm64_thunderx_linuxapp_gcc b/config/arm/arm64_thunderx_linuxapp_gcc
index 7ff34af74..967d9d46d 100644
--- a/config/arm/arm64_thunderx_linuxapp_gcc
+++ b/config/arm/arm64_thunderx_linuxapp_gcc
@@ -2,6 +2,7 @@
 c = 'aarch64-linux-gnu-gcc'
 cpp = 'aarch64-linux-gnu-cpp'
 ar = 'aarch64-linux-gnu-gcc-ar'
+strip = 'aarch64-linux-gnu-strip'
 
 [host_machine]
 system = 'linux'
-- 
2.11.0

  parent reply	other threads:[~2018-06-14  9:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1527133127-29407-1-git-send-email-gavin.hu@arm.com>
2018-05-24  3:38 ` [dpdk-stable] [PATCH 1/2] mk: fix cross build errors Gavin Hu
2018-05-28  6:53 ` [dpdk-stable] [PATCH v2 " Gavin Hu
2018-05-28 13:24   ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2018-05-29  1:22     ` Gavin Hu
2018-05-29  6:51   ` [dpdk-stable] [PATCH v3 " Gavin Hu
     [not found]     ` <1527578508-27297-1-git-send-email-gavin.hu@arm.com>
2018-05-29  7:21       ` [dpdk-stable] [PATCH v4 " Gavin Hu
     [not found]       ` <1527590616-28299-1-git-send-email-gavin.hu@arm.com>
2018-05-29 10:43         ` [dpdk-stable] [PATCH v5 " Gavin Hu
2018-05-29 15:09           ` Thomas Monjalon
     [not found]         ` <20180614095127.16245-1-gavin.hu@arm.com>
2018-06-14  9:51           ` [dpdk-stable] [PATCH v6 1/7] " Gavin Hu
2018-06-14  9:51           ` [dpdk-stable] [PATCH v6 3/7] devtools: fix the Exec format error Gavin Hu
2018-06-14 10:34             ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2018-06-15  8:07               ` Gavin Hu
2018-06-14  9:51           ` Gavin Hu [this message]
2018-06-14 10:34             ` [dpdk-stable] [dpdk-dev] [PATCH v6 4/7] build: fix the meson build warning Bruce Richardson
2018-06-14  9:51           ` [dpdk-stable] [PATCH v6 5/7] devtools: fix the missing ninja command error on CentOS Gavin Hu
2018-06-14 10:40             ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2018-06-15  8:08               ` Gavin Hu
2018-06-14  9:51           ` [dpdk-stable] [PATCH v6 6/7] build: fix the meson cross compile error Gavin Hu
2018-06-14 10:42             ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2018-06-14  9:51           ` [dpdk-stable] [PATCH v6 7/7] devtools: expand meson cross compiling coverage Gavin Hu
2018-06-14 10:45             ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2018-06-15  8:09               ` Gavin Hu
2018-06-15 10:23               ` Gavin Hu

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=20180614095127.16245-5-gavin.hu@arm.com \
    --to=gavin.hu@arm.com \
    --cc=dev@dpdk.org \
    --cc=stable@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).