From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-users] DPDK 16.04 link changes cause PMD
	drivers to not be loaded
Date: Thu, 21 Apr 2016 17:18:16 +0200
Message-ID: <2358356.HZLcvC2y3R@xps13>
References: <57158D01.5020407@cs.berkeley.edu> <571895D9.3090700@redhat.com>
 <5718EB59.5010808@cs.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, Panu Matilainen <pmatilai@redhat.com>
To: apanda@cs.berkeley.edu
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51])
 by dpdk.org (Postfix) with ESMTP id 93B612C18
 for <dev@dpdk.org>; Thu, 21 Apr 2016 17:18:38 +0200 (CEST)
Received: by mail-wm0-f51.google.com with SMTP id v188so249219380wme.1
 for <dev@dpdk.org>; Thu, 21 Apr 2016 08:18:38 -0700 (PDT)
In-Reply-To: <5718EB59.5010808@cs.berkeley.edu>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-04-21 08:01, Aurojit Panda:
> Panu Matilainen wrote:
[...]
> > Again, PMDs are *plugins* that are *meant* to be loaded at runtime.
> > That allows for all sorts of flexibility especially
> > for packaging and shipping, at some extra cost in setup complexity.
> 
> I am all for a plugin architecture, I was merely suggesting that you
> embed some path infromation at the beginning. Also please note:
> (a) This behavior changed recently.

What changed recently?

> (b) This change is entirely undocumented, which is why I was reporting
> it in the first place.
> (c) It is actually quite unintutive, because previously ensuring
> LD_LIBRARY_PATH was correct was all that was required 
> to get any DPDK application to interact with ports.

?
Are you talking about combined library?

> > For your own purposes, you can of course tweak the linking settings
> > as much as you like. Look for "plugins" in mk/rte.app.mk and change
> > the shared lib condition on the line above to "y" and there you have it.
> > But that's not the way plugins are meant to be used.
> 
> That is not a reasonable solution given that it makes it very hard to
> track future changes to DPDK without merges.
> My alternatives neither break people's abilities to use plugins,
> nor do they impact behavior.

Please do not hesitate to send some patch to show your solution.
Thanks