From: Stephen Hemminger <stephen@networkplumber.org>
To: "Simon Kågström" <simon.kagstrom@netinsight.net>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
jerin.jacob@caviumnetworks.com, jianbo.liu@linaro.org
Subject: Re: librte_table build race with SYMLINK-FILE?
Date: Mon, 11 Apr 2016 11:15:31 -0700 [thread overview]
Message-ID: <20160411111531.5044d1d9@xeon-e3> (raw)
In-Reply-To: <570B8078.7060409@netinsight.net>
On Mon, 11 Apr 2016 12:46:16 +0200
Simon Kågström <simon.kagstrom@netinsight.net> wrote:
> Hi!
>
> I'm upgrading from DPDK 2.1 to 16.04-rc4, and have a new build issue
> which I didn't see before. It's in the librte_table and happens from
> time to time (unfrequently) in my out-of-tree build. It looks like a
> race between comilation and SYMLINK-FILE:
>
> [...]
> == Build lib/librte_table
> CC rte_table_lpm_ipv6.o
> CC rte_table_lpm.o
> CC rte_table_acl.o
> CC rte_table_hash_key8.o
> In file included from [...]lib/librte_table/rte_table_lpm.c:43:0:
> [...]/dpdk.build/include/rte_lpm.h:484:25: fatal error: rte_lpm_sse.h:
> No such file or directory
> #include "rte_lpm_sse.h"
> ^
> compilation terminated.
> CC rte_table_hash_key16.o
> [...]
>
> In this case, rte_lpm_sse.h is optionally symlinked if we're not on ARM.
> I've tried patching away the issue by unconditionally symlinking the
> _{neon,sse}.h files, and while I don't see the problem after that, I
> don't really see why it would improve the situation.
>
> Does anyone else see this as well?
>
> // Simon
The issue is a missing dependency in the mk file for LPM.
next prev parent reply other threads:[~2016-04-11 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 10:46 librte_table build race with SYMLINK-FILE? Simon Kågström
2016-04-11 18:15 ` Stephen Hemminger [this message]
2016-04-11 18:53 ` Thomas Monjalon
2016-04-12 12:05 ` Simon Kågström
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=20160411111531.5044d1d9@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@linaro.org \
--cc=simon.kagstrom@netinsight.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.