public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/3] Remove --enable-obsolete-nsl configure flag
Date: Wed, 8 Jul 2020 06:16:28 -0700	[thread overview]
Message-ID: <20200708131628.GA3289@gmail.com> (raw)
In-Reply-To: <cf1f91271d178a79916f2d734ffbf4593cef5ee0.1594209330.git.fweimer@redhat.com>

On Wed, Jul 08, 2020 at 02:05:56PM +0200, GNU C Library wrote:
> From: Petr Vorel <pvorel@suse.cz>
> 
> this means that *always* libnsl is only built as shared library for
> backward compatibility and the NSS modules libnss_nis and libnss_nisplus
> are not built at all, libnsl's headers aren't installed.
> 
> This compatibility is kept only for architectures and ABIs that have
> been added in or before version 2.28.
> 
> Replacement implementations based on TIRPC, which additionally support
> IPv6, are available from <https://github.com/thkukuk/>.
> 
> This change does not affect libnss_compat which does not depended
> on libnsl since 2.27 and thus can be used without NIS.
> 
> libnsl code depends on Sun RPC, e.g. on --enable-obsolete-rpc (installed
> libnsl headers use installed Sun RPC headers), which will be removed in
> the following commit.

Without --enable-obsolete-nsl nor --enable-obsolete-rpc, are the installed
glibc binaries and header files the same as before this patch, excluding
debug info?  If the answer is yes, it is OK.

Thanks.

H.J.

  reply	other threads:[~2020-07-08 13:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 12:05 [PATCH 0/3] sunrpc removal Florian Weimer
2020-07-08 12:05 ` [PATCH 1/3] Move non-deprecated RPC-related functions from sunrpc to inet Florian Weimer
2020-07-08 12:21   ` Andreas Schwab
2020-07-08 12:23     ` Florian Weimer
2020-07-08 12:56   ` H.J. Lu
2020-07-08 12:05 ` [PATCH 2/3] Remove --enable-obsolete-nsl configure flag Florian Weimer
2020-07-08 13:16   ` H.J. Lu [this message]
2020-07-08 14:55     ` Florian Weimer
2020-07-08 14:57       ` H.J. Lu
2020-07-08 15:22         ` Florian Weimer
2020-07-08 15:23           ` H.J. Lu
2020-07-08 12:06 ` [PATCH 3/3] Remove --enable-obsolete-rpc " Florian Weimer
2020-07-08 13:17   ` H.J. Lu
2020-07-10  9:58   ` Petr Vorel
2020-07-10 10:48     ` Florian Weimer
2020-07-10 10:56       ` Petr Vorel
2020-07-08 13:02 ` [PATCH 0/3] sunrpc removal H.J. Lu
2020-07-08 13:06   ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200708131628.GA3289@gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).