From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: librte_table build race with SYMLINK-FILE? Date: Mon, 11 Apr 2016 11:15:31 -0700 Message-ID: <20160411111531.5044d1d9@xeon-e3> References: <570B8078.7060409@netinsight.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org, bruce.richardson@intel.com, jerin.jacob@caviumnetworks.com, jianbo.liu@linaro.org To: Simon =?UTF-8?B?S8OlZ3N0csO2bQ==?= Return-path: Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by dpdk.org (Postfix) with ESMTP id 6C459DE0 for ; Mon, 11 Apr 2016 20:15:22 +0200 (CEST) Received: by mail-pa0-f45.google.com with SMTP id td3so125898216pab.2 for ; Mon, 11 Apr 2016 11:15:22 -0700 (PDT) In-Reply-To: <570B8078.7060409@netinsight.net> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, 11 Apr 2016 12:46:16 +0200 Simon K=C3=A5gstr=C3=B6m wrote: > Hi! >=20 > 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: >=20 > [...] > =3D=3D 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 > [...] >=20 > 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. >=20 > Does anyone else see this as well? >=20 > // Simon The issue is a missing dependency in the mk file for LPM.