[PATCH] Remove compat from DEFAULT_CONFIG lookup strings
Joseph Myers
joseph@codesourcery.com
Fri Aug 18 22:12:00 GMT 2017
On Fri, 18 Aug 2017, Steve Ellcey wrote:
> On Fri, 2017-08-18 at 21:12 +0000, Joseph Myers wrote:
> > On Fri, 18 Aug 2017, Steve Ellcey wrote:
> >
> > >
> > > I would think so. Â I did a search and didn't find any more "compat"
> > > lookups beyond what you found. Â Not doing these changes didn't cause
> > > any testsuite failures but it does seem like they should be changed. Â I
> > > updated them and reran the testsuite and got no regressions. Â Here is
> > > an updated patch.
> > Does this affect any defaults visible to glibc users?  If it does, itÂ
> > needs an entry in the "Deprecated and removed features, and other changesÂ
> > affecting compatibility" section of NEWS.
>
> I think everything is already in the 2.26 Depreciated section. Â This
> was done when the original patch to remove libnss_compat was made.
> These changes are just dealing with the fact that that patch was
> incomplete.
But the impression that NEWS entry gives is that you can use
--enable-obsolete-nsl to get back the previous semantics. Does your patch
change the semantics in the --enable-obsolete-nsl case?
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libc-alpha
mailing list