This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [Libtirpc-devel] Fwd: Re: proposed patch to rpcbind to providefiner-grained security controls than offered by the -i option
- From: Ulrich Drepper <drepper at gmail dot com>
- To: Chuck Lever <chucklever at gmail dot com>
- Cc: Steve Dickson <SteveD at redhat dot com>, libc-alpha at sourceware dot org, libtirpc <libtirpc-devel at lists dot sourceforge dot net>
- Date: Mon, 13 Dec 2010 12:31:07 -0500
- Subject: Re: [Libtirpc-devel] Fwd: Re: proposed patch to rpcbind to providefiner-grained security controls than offered by the -i option
- References: <4D0632C5.1040107@RedHat.com> <AANLkTi=FNANqAs5m3xbZcQq5K0vMtZBb1+KU9pWC9K8_@mail.gmail.com>
On Mon, Dec 13, 2010 at 10:29, Chuck Lever <chucklever@gmail.com> wrote:
> Is it possible to create a build-time option to include the RPC
> implementation in glibc, and to install the RPC headers and man pages
> at install time?
The concept of binary compatibility seems to be completely alien to
you. No, there cannot be an option to leave out code which has been
there before without breaking compatibility.
What is possible is to prevent the linker from using the definitions
in libc. It would be as if the symbols aren't there anymore but
existing programs would continue to work. I'm open to implement this
for a future release.