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: Tue, 2 Jun 2020 14:38:09 +0530 [thread overview]
Message-ID: <CALBAE1MZw1tK5tdP138vrBjgdygmJuKmf-8tmJ4=KtqtMrAM0g@mail.gmail.com> (raw)
In-Reply-To: <c3e7ce76c3ec451dbb783d28c2efaccd@pantheon.tech>
On Tue, Jun 2, 2020 at 12:43 PM Juraj Linkeš <juraj.linkes@pantheon.tech> wrote:
>
> Hi Jerin,
>
> I forgot to mention that I'm using GCC 8 and this fixed the issue. A bit of googling illuminated why this could be so, according to https://gcc.gnu.org/onlinedocs/cpp/Include-Syntax.html, the angle brackets directive looks for files in a standard list of system directories while the quotes directive looks in the directory containing the current file first. What it doesn't really explain is the random failues. Any idea why it sometimes built fine and sometimes it errored? Some race condition perhaps?
it is racy due to the fact that rte_ethdev_core.h need to show up in
build/include/ before .c file compiles in order to make #include <>
works. In case of #include "", that dependency is not there.
Makefile file infrastructure is not defining the dependency anywhere.
>
> Thanks,
> Juraj
>
> -----Original Message-----
> From: Jerin Jacob <jerinjacobk@gmail.com>
> Sent: Monday, June 1, 2020 4:37 PM
> To: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Non-deterministic build failure in rte_ethdev.h:4287:10 on Taishan ARM server
>
> 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
> >
prev parent reply other threads:[~2020-06-02 9:08 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
2020-06-02 7:13 ` Juraj Linkeš
2020-06-02 9:08 ` Jerin Jacob [this message]
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='CALBAE1MZw1tK5tdP138vrBjgdygmJuKmf-8tmJ4=KtqtMrAM0g@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).