Re: [PATCH] deprecate libnsl (Version 4)

[Thorsten Kukuk <kukuk at suse dot de>]

On Thu, Feb 23, Zack Weinberg wrote:

> There are a lot of configure scripts out there that do
> AC_CHECK_LIB([nsl], [gethostbyname]).  Yes, that should be
> AC_SEARCH_LIBS, the Autoconf manual even says so these days, but some
> people are still using autoconf 2.13, so.  Would you please verify
> that an autoconf script with AC_CHECK_LIB([nsl], [gethostbyname]) in
> it does _not_ fail when run against a glibc with this modification,
> and the generated makefile does _not_ try to link -lnsl?

Depends on what you understand under "fail":

checking for gethostbyname in -lnsl... no
checking that generated files are newer than configure... done
configure: creating ./config.status

And of course does the Makefile not try in this case to link against
libnsl, while with libnsl, it will link against libnsl even if not
needed. No change compared to today.

> The NEWS entry should explain which programs are likely to need your
> libnsl replacement.  It's my impression that the answer is "almost
> none", but it's important to be reassuring here.

There is no change in which applications needs libnsl or not compared
to today with glibc. My libnsl replacement is a 1:1 replacement of the
current version of glibc, the API is 100% compatible. The only difference
between the two libraries is, that my new libnsl will use the TIRPC
interface and thus works with IPv6. Completly transparent for the
applications linked against libnsl.
So everything which needs glibc libnsl, would need my libnsl.

  Thorsten

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)