[dpdk-dev] [PATCH 1/1] eal: Don't fail secondary if primary is missing tailqs

[Burakov, Anatoly]

On 13-Nov-18 9:21 AM, Thomas Monjalon wrote:
> 13/11/2018 00:33, Burdick, Cliff:
>> This patch was submitted by Jean Tourrilhes over two years ago, but didn't receive any responses. I hit the same issue recently when trying to use cgo (Golang) as a primary process linked to libdpdk.a against a C++ application linked against the same library.
> 
> The question is to know why you don't have the same constructors in primary and seconday?
> 

I've hit similar things in the past. I believe it was caused by our 
build system stripping out unused libraries (such as rte_hash) from the 
binary and thus not calling the constructor in the primary, but doing so 
in the secondary (or something to that effect). In any case, this is 
caused by linking different number of libraries to primary and 
secondary, and should probably be fixed in the build system, not in the 
tailqs code (unless we specifically support having different linked 
libraries to primary and secondary?).

-- 
Thanks,
Anatoly