From: Thomas Monjalon <thomas@monjalon.net>
To: Aaron Conole <aconole@redhat.com>
Cc: honnappa.nagarahalli@arm.com, ruifeng.wang@arm.com,
gavin.hu@arm.com, dharmik.thakkar@arm.com,
jerin.jacob@caviumnetworks.com, Yongseok Koh <yskoh@mellanox.com>,
dev@dpdk.org, msantana@redhat.com, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] DPDK compilation on arm is failing in Travis
Date: Wed, 05 Jun 2019 22:04:53 +0200 [thread overview]
Message-ID: <74282465.H2CcKukIUE@xps> (raw)
In-Reply-To: <f7t1s07om62.fsf@dhcp-25.97.bos.redhat.com>
05/06/2019 21:40, Aaron Conole:
> Thomas Monjalon <thomas@monjalon.net> 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
I see the error now.
It is printing the full log after the error,
so I missed the error at the top.
I've read your comment about a possible error with the patch
removing weak functions but neither me nor Bruce were able
to reproduce it. What is the condition to see this compiler warning?
next prev parent reply other threads:[~2019-06-05 20:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 18:26 Thomas Monjalon
2019-06-05 19:40 ` Aaron Conole
2019-06-05 20:04 ` Thomas Monjalon [this message]
2019-06-05 20:58 ` Aaron Conole
2019-06-05 21:05 ` Honnappa Nagarahalli
2019-06-05 21:36 ` Honnappa Nagarahalli
2019-06-05 22:38 ` Michael Santana Francisco
2019-06-06 4:42 ` Honnappa Nagarahalli
2019-06-06 14:50 ` Aaron Conole
2019-06-07 5:10 ` Honnappa Nagarahalli
2019-06-07 13:24 ` Aaron Conole
2019-06-07 13:53 ` Honnappa Nagarahalli
2019-06-08 8:38 ` Jerin Jacob Kollanukkaran
2019-06-08 8:41 ` Jerin Jacob Kollanukkaran
2019-06-06 14:57 ` Jerin Jacob Kollanukkaran
2019-06-06 17:06 ` Michael Santana Francisco
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=74282465.H2CcKukIUE@xps \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dharmik.thakkar@arm.com \
--cc=gavin.hu@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=msantana@redhat.com \
--cc=ruifeng.wang@arm.com \
--cc=yskoh@mellanox.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 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).