They are: [3:15am] 97>nm /usr/lib/libc.so | grep xdr_longlong 000000000014ffe2 T _xdr_longlong_t 000000000014ffe2 W xdr_longlong_t [3:15am] 98>nm /usr/lib/libc.so | grep xdr_hyper 000000000014ff0a T _xdr_hyper 000000000014ff0a W xdr_hyper I've also changed time_type to be long long and the surrounding code to do xdd_longlong_t. It works fine, but there is a compatibility issue. I guess we could bump the version of the rpc protocol and provide compatibility functions, but I think it is overkill. I would just make the incompatible changes. christos > On Aug 23, 2022, at 1:55 AM, rvp%sdf.org@localhost <rvp%SDF.ORG@localhost> wrote: > >> Number: 56977 >> Category: lib >> Synopsis: xdr: no implementation for xdr_hyper(3) etc. >> Confidential: no >> Severity: non-critical >> Priority: low >> Responsible: lib-bug-people >> State: open >> Class: change-request >> Submitter-Id: net >> Arrival-Date: Mon Aug 22 22:55:01 +0000 2022 >> Originator: RVP >> Release: NetBSD-HEAD and 9.X >> Organization: >> Environment: > NetBSD x202e.localdomain 9.99.98 NetBSD 9.99.98 (GENERIC) #0: Tue Jun 21 12:20:43 UTC 2022 mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd64 >> Description: > The xdr(3) manpages mentions xdr_hyper(), xdr_longlong_t() etc., but these don't seem to be implemented. > > Would be nice to have these to transport 64-bit timestamps around. >> How-To-Repeat: > >> Fix: > OpenBSD has 'em...
Attachment:
signature.asc
Description: Message signed with OpenPGP