On Thu, 2018-10-04 at 16:43 +0100, Ferruh Yigit wrote: > Enabling RTE_NEXT_ABI means to enable APIs that break the ABI for > the current release and these APIs are targetted for further release. > > RTE_NEXT_ABI shouldn't be enabled by default. > > Signed-off-by: Ferruh Yigit <ferruh.yi...@intel.com> > --- > Cc: Neil Horman <nhor...@tuxdriver.com> > Cc: Thomas Monjalon <tho...@monjalon.net> > Cc: Luca Boccassi <bl...@debian.org> > Cc: Christian Ehrhardt <christian.ehrha...@canonical.com> > --- > config/common_base | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/config/common_base b/config/common_base > index 2e888d13b..dbd0c9ae9 100644 > --- a/config/common_base > +++ b/config/common_base > @@ -43,7 +43,7 @@ CONFIG_RTE_BUILD_SHARED_LIB=n > # > # Use newest code breaking previous ABI > # > -CONFIG_RTE_NEXT_ABI=y > +CONFIG_RTE_NEXT_ABI=n > > # > # Major ABI to overwrite library specific LIBABIVER
Acked-by: Luca Boccassi <bl...@debian.org> -- Kind regards, Luca Boccassi
