Re: [dpdk-dev] [PATCH] app: fix plugin load on static builds

2020-11-26 Thread Bruce Richardson
On Thu, Nov 26, 2020 at 05:32:26PM +0100, Olivier Matz wrote: > Hi Bruce, > > Thanks for the feedback. > > On Thu, Nov 26, 2020 at 03:28:46PM +, Bruce Richardson wrote: > > On Thu, Nov 26, 2020 at 03:20:42PM +0100, Olivier Matz wrote: > > > When dpdk is compiled as static libraries, it is not

Re: [dpdk-dev] [PATCH] app: fix plugin load on static builds

2020-11-26 Thread Olivier Matz
Hi Bruce, Thanks for the feedback. On Thu, Nov 26, 2020 at 03:28:46PM +, Bruce Richardson wrote: > On Thu, Nov 26, 2020 at 03:20:42PM +0100, Olivier Matz wrote: > > When dpdk is compiled as static libraries, it is not possible > > to load a plugin from an application. We get the following err

Re: [dpdk-dev] [PATCH] app: fix plugin load on static builds

2020-11-26 Thread Bruce Richardson
On Thu, Nov 26, 2020 at 03:20:42PM +0100, Olivier Matz wrote: > When dpdk is compiled as static libraries, it is not possible > to load a plugin from an application. We get the following error: > > EAL: librte_pmd_.so: undefined symbol: per_lcore__rte_errno > > This happens because the dpdk

[dpdk-dev] [PATCH] app: fix plugin load on static builds

2020-11-26 Thread Olivier Matz
When dpdk is compiled as static libraries, it is not possible to load a plugin from an application. We get the following error: EAL: librte_pmd_.so: undefined symbol: per_lcore__rte_errno This happens because the dpdk symbols are not exported. Add them to the dynamic symbol table by using '