[dpdk-dev] weak functions in some drivers
Sergio Gonzalez Monroy
sergio.gonzalez.monroy at intel.com
Thu Jun 30 10:14:53 CEST 2016
On 29/06/2016 14:26, Elo, Matias (Nokia - FI/Espoo) wrote:
>>> What is not clear to me is motivation to use weak here instead of simply using >CONFIG_RTE_I40E_INC_VECTOR
>>> macro to exclude stubs in i40e_rxtx.c. It will make library smaller and avoid issues like this one
>>> which are quite hard to troubleshoot.
>> Since this issue seen in fd.io, I didn't investigated more, but I don't
>> want to clock your valid question, this is an attempt to resurrect the
>> question ...
> We are having exactly the same problem. For us the aforementioned workaround doesn't seem to work and vector mode is always disabled with the i40e drivers. If I modify i40e_rxtx.c and exclude the stub functions using CONFIG_RTE_I40E_INC_VECTOR everything works as expected.
> We are building DPDK with the CONFIG_RTE_BUILD_COMBINE_LIBS option enabled and link DPDK library to our application.
> Any other ideas how this could be fixed?
So you have tried to link a combined static lib with --whole-archive
-ldpdk --no-whole-archive and still get the wrong/weak function definition?
More information about the dev