From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Non-deterministic build failure in rte_ethdev.h:4287:10 on Taishan ARM server
Date: Mon, 1 Jun 2020 20:06:48 +0530 [thread overview]
Message-ID: <CALBAE1MA2QZgJSKXT1SdJmQZAw1P9Tw2+JTT8qHhQ3W1SOibDA@mail.gmail.com> (raw)
In-Reply-To: <b541ad8242834f50a3ebd0a0639cf8dd@pantheon.tech>
On Mon, Jun 1, 2020 at 6:15 PM Juraj Linkeš <juraj.linkes@pantheon.tech> wrote:
>
> Hi DPDK devs,
>
> I'm hitting a build failure with dpdk 20.02.1 with rte_ethdev.h that's happening seemingly at random:
> make install T=arm64-armv8a-linuxapp-gcc -j
> In file included from /tmp/openvpp-testing/dpdk/lib/librte_ethdev/rte_class_eth.c:13:0:
> /tmp/openvpp-testing/dpdk/lib/librte_ethdev/rte_ethdev.h:4287:10: fatal error: rte_ethdev_core.h: No such file or directory
> #include <rte_ethdev_core.h>
> ^~~~~~~~~~~~~~~~~~~
Try as #include "rte_ethdev_core.h" instead of #include <rte_ethdev_core.h>
> compilation terminated.
> make[5]: *** [rte_class_eth.o] Error 1
> make[5]: *** Waiting for unfinished jobs....
> make[4]: *** [librte_ethdev] Error 2
> make[3]: *** [lib] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [pre_install] Error 2
> make: *** [install] Error 2
>
> Full log here: https://logs.fd.io/production/vex-yul-rot-jenkins-1/csit-dpdk-perf-verify-master-3n-tsh/11/archives/log.html.gz
>
next prev parent reply other threads:[~2020-06-01 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 12:45 Juraj Linkeš
2020-06-01 14:36 ` Jerin Jacob [this message]
2020-06-02 7:13 ` Juraj Linkeš
2020-06-02 9:08 ` Jerin Jacob
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=CALBAE1MA2QZgJSKXT1SdJmQZAw1P9Tw2+JTT8qHhQ3W1SOibDA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
/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).