F15's /usr/include/rpc has disappeared; <netdb.h> uncompilable
Josh Boyer
jwboyer at gmail.com
Fri May 6 10:38:11 UTC 2011
On Thu, May 5, 2011 at 10:32 PM, Dave Airlie <airlied at redhat.com> wrote:
> On Thu, 2011-05-05 at 10:52 -0600, Pete Zaitcev wrote:
>> On Thu, 05 May 2011 15:39:21 +0200
>> Jim Meyering <jim at meyering.net> wrote:
>>
>> > Reported as http://bugzilla.redhat.com/702366
>> > and http://bugzilla.redhat.com/702354
>>
>> Well, here's NEWS:
>>
>> > * The RPC implementation in libc is obsoleted. Old programs keep working
>> > but new programs cannot be linked with the routines in libc anymore.
>> > Programs in need of RPC functionality must be linked against TI-RPC.
>> > The TI-RPC implemtation is IPv6 enabled and there are other benefits.
>> >
>> > Visible changes of this change include (obviously) the inability to link
>> > programs using RPC functions without referencing the TI-RPC library, the
>> > removal of the RPC headers from the glibc headers, and the lack of
>> > symbols defined in <rpc/netdb.h> when <netdb.h> is installed.
>> > Implemented by Ulrich Drepper.
>>
>> The question is: what is TI-RPC and where one finds it?
>> Is it even packaged in Fedora?
>
> No the question is what do the glibc maintainers think they are doing
> introducing changes like this in a branched release. This sort of stuff
> should be in rawhide.
>
> These guys are in no way useful at helping create a distro, can we
> request a fedora glibc maintainer who understands how to follow a
> release schedule.
The largest problem comes from upstream glibc using the Fedora
schedule as their development schedule. So 2.13.90 will become 2.14
shortly after Fedora 15 reaches RC. (I've asked a number of times for
it to release _before_ RC, but no luck there). My assumption is that
pre-release Fedora users are being used as glibc beta testers to get
broader coverage.
josh
More information about the devel
mailing list