Re: [Y2038] Trying Debian/armhf rebootstrap with time64
- To: Ben Hutchings <ben.hutchings@codethink.co.uk>
- Cc: Arnd Bergmann <arnd@arndb.de>, Rich Felker <dalias@libc.org>, Riku Voipio <riku.voipio@iki.fi>, GNU C Library <libc-alpha@sourceware.org>, y2038 Mailman List <y2038@lists.linaro.org>, Helmut Grohne <helmutg@debian.org>, tcwg@linaro.org, debian-arm@lists.debian.org, Wookey <wookey@wookware.org>, Jan Kiszka <jan.kiszka@web.de>, Steve McIntyre <steve@einval.com>
- Subject: Re: [Y2038] Trying Debian/armhf rebootstrap with time64
- From: Florian Weimer <fw@deneb.enyo.de>
- Date: Fri, 20 Mar 2020 00:09:47 +0100
- Message-id: <[🔎] 87sgi4djr8.fsf@mid.deneb.enyo.de>
- In-reply-to: <[🔎] 41b124aa75b5ff1cf328390e32ad912e3f0d5d04.camel@codethink.co.uk> (Ben Hutchings's message of "Thu, 19 Mar 2020 22:49:45 +0000")
- References: <[🔎] CAK8P3a0EtmgDRbDzBhOOZk_kyWmCm1aqvSxwUeY0R7tbCSxaKg@mail.gmail.com> <20200313202234.GA3980@brightrain.aerifal.cx> <[🔎] CAK8P3a0eDr5d1s9mqfs7HXXeCMAT7=dxftbM91ny0f6fAd3Zjg@mail.gmail.com> <20200316144719.GU11469@brightrain.aerifal.cx> <[🔎] CAK8P3a14=JZfOz26utwFd4P2Fj7EkCZUsQXfr=Vz+bth_G0QeQ@mail.gmail.com> <[🔎] 41b124aa75b5ff1cf328390e32ad912e3f0d5d04.camel@codethink.co.uk>
* Ben Hutchings:
> On Mon, 2020-03-16 at 16:02 +0100, Arnd Bergmann wrote:
>> On Mon, Mar 16, 2020 at 3:47 PM Rich Felker <dalias@libc.org> wrote:
>>
>> > libtirpc is the replacement. I wasn't aware if uses libc-provided rpc
>> > headers (presumably only if they exist, since folks are using it fine
>> > on musl) but even if so I think the types will automatically update
>> > when time_t changes. Of course that leaves the libtirpc ABI dependent
>> > on which time_t is used.
>>
>> Ok, makes sense. I suppose it just provides a header with the same
>> name then.
>
> * nfs-utils build-depends on libtirpc-dev, and isn't using the glibc
> SunRPC headers except for <rpc/netdb.h>. libtirpc's <rpc/rpcent.h>
> specifically avoids declaring things that are also declared in glibc's
> <rpc/netdb.h>.
>
> * ntirpc is a different port of the SunRPC code, used by nfs-ganesha.
>
> * nis and nfswatch really are using the glibc SunRPC headers.
Which part of NIS? There's a new upstream for libnsl
<https://github.com/thkukuk/libnsl> and the NSS module
<https://github.com/thkukuk/libnss_nis>. (There is a nisplus module
as well.)
All these use libtirpc and support IPv6 in addition to IPv4. As far
as I know, it is possible to build a full NIS stack without relying on
any of the legacy glibc code.
(I don't know about nfswatch.)
Reply to: