This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: deprecated sunrpc and rpc/netdb.h
- From: Thorsten Kukuk <kukuk at suse dot de>
- To: libc-alpha at sourceware dot org
- Date: Thu, 17 Mar 2016 19:41:54 +0100
- Subject: Re: deprecated sunrpc and rpc/netdb.h
- Authentication-results: sourceware.org; auth=none
- References: <20160316100021 dot GA8341 at suse dot de> <mvmy49ig0wz dot fsf at hawking dot suse dot de> <20160316141808 dot GJ6588 at vapier dot lan> <20160316143302 dot GA2794 at suse dot de> <20160316192823 dot GM6588 at vapier dot lan> <20160317104841 dot GA32414 at suse dot de> <20160317145150 dot GR6588 at vapier dot lan> <20160317150149 dot GA21496 at suse dot de> <20160317181106 dot GV6588 at vapier dot lan> <20160317181420 dot GW6588 at vapier dot lan>
On Thu, Mar 17, Mike Frysinger wrote:
> > the smooth transition plan is for tirpc to provide the full API. if
tirpc should do this. At least I'm not aware about any missing ones.
> > glibc turns off the exported symbols (which --disable-obsolete-rpc
> > does), then there is no "smooth" transition -- your code fails to link
> > entirely if you aren't supporting tirpc. stub headers do not make it
> > any easier ... if anything, it makes it harder.
The problem is, that glibc neither fully disables rpc nor
that the NSS functionality can be provided by third party
implementation.
But as long as you refuse to dicuss any realistic solution
to solve this, nothing will change.
> > i'm fully aware of the level of pain seen in distros as i've sent/made
> > many patches to packages that are in Gentoo.
Why didn't you fix the original problem?
With a correct solution of rpc/netdb.h in glibc, I only need
to link against libtirpc. I haven't found any package yet,
which needs other code changes. They may exist, but not in
the base system I'm using.
> to clarify: the *only* reason Gentoo didn't leave RPC disabled in glibc
> is purely because libtirpc isn't a full replacement. as soon as that
> situation changes, RPC is being disabled in Gentoo's glibc.
I asked several times here on the mailing list, what this problems
should be. Until no, nobody did come up with any example, including
you.
> also: nothing is stopping you from *today* sending fixes to projects to
> have them use libtirpc. that'll work regardless of the glibc status.
A more solution based discussion would be much more helpfull.
As I wrote: with the current rpc/netdb.h situation with glibc,
it is impossible to find an always working solution with the
same functionality as today.
Thorsten
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)