From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id A211EA0096 for ; Wed, 5 Jun 2019 21:41:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 93E961B94D; Wed, 5 Jun 2019 21:41:35 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id EE8C61B947 for ; Wed, 5 Jun 2019 21:41:33 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 4D4245946B; Wed, 5 Jun 2019 19:40:59 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (unknown [10.18.25.61]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CAEFA619A1; Wed, 5 Jun 2019 19:40:53 +0000 (UTC) From: Aaron Conole To: Thomas Monjalon Cc: honnappa.nagarahalli@arm.com, ruifeng.wang@arm.com, gavin.hu@arm.com, dharmik.thakkar@arm.com, jerin.jacob@caviumnetworks.com, Yongseok Koh , dev@dpdk.org, msantana@redhat.com References: <18576498.0Zn3BvHS7Y@xps> Date: Wed, 05 Jun 2019 15:40:53 -0400 In-Reply-To: <18576498.0Zn3BvHS7Y@xps> (Thomas Monjalon's message of "Wed, 05 Jun 2019 20:26:01 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Wed, 05 Jun 2019 19:41:21 +0000 (UTC) Subject: Re: [dpdk-dev] DPDK compilation on arm is failing in Travis X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Thomas Monjalon writes: > The compilation of the master branch is failing for aarch64: > https://travis-ci.com/DPDK/dpdk > The log is so much verbose that I am not able to understand > what is really wrong. > Please help to diagnose and fix, thanks. A discussion about this: http://mails.dpdk.org/archives/dev/2019-June/134012.html