2017-03-01 15:35, Jan Blunck: > On Wed, Mar 1, 2017 at 10:34 AM, Christian Ehrhardt > <christian.ehrha...@canonical.com> wrote: > > Downstreams might want to provide different DPDK releases at the same > > time to support multiple consumers of DPDK linked against older and newer > > sonames. > > > > Also due to the interdependencies that DPDK libraries can have applications > > might end up with an executable space in which multiple versions of a > > library are mapped by ld.so. > > > > Think of LibA that got an ABI bump and LibB that did not get an ABI bump > > but is depending on LibA. > > > > Application > > \-> LibA.old > > \-> LibB.new -> LibA.new > > > > That is a conflict which can be avoided by setting CONFIG_RTE_MAJOR_ABI. > > If set CONFIG_RTE_MAJOR_ABI overwrites any LIBABIVER value. > > An example might be ``CONFIG_RTE_MAJOR_ABI=16.11`` which will make all > > libraries librte<?>.so.16.11 instead of librte<?>.so.<LIBABIVER>. [...] > > > > Signed-off-by: Christian Ehrhardt <christian.ehrha...@canonical.com> > > Reviewed-by: Jan Blunck <jblu...@infradead.org> > Tested-by: Jan Blunck <jblu...@infradead.org>
Not sure about how it can be used in distributions, but it does not hurt to provide the config option. Are you going to link applications against a fixed DPDK version for every libraries? Applied, thanks
