From: Florian Weimer <fweimer@redhat.com>
To: Yair Lenga via Libc-help <libc-help@sourceware.org>
Cc: Yair Lenga <yair.lenga@gmail.com>
Subject: Re: sunrpc and rpcgen code
Date: Mon, 25 Jul 2022 17:48:52 +0200 [thread overview]
Message-ID: <87h735p50b.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAK3_KpMs0Ar94UA3xXVu1pBa=dq++fhbJfFX-YJrai6Drd4WsA@mail.gmail.com> (Yair Lenga via Libc-help's message of "Mon, 25 Jul 2022 18:33:35 +0300")
* Yair Lenga via Libc-help:
> The current glibc library includes a version of the sunrpc (a.k.a oncrpc)
> rpc library, and the 'rpcgen' utility, used to translate ".x" files
> into rpc clients/server stubs. I recall a few years ago, there were some
> discussions about splitting those components from glibc into separate
> packages.
I believe the de-facto replacement is here:
<https://github.com/thkukuk/rpcsvc-proto/>
This package contains rpcsvc proto.x files from glibc, which are
missing in libtirpc. Additional it contains rpcgen, which is needed
to create header files and sources from protocol files.
This package is only needed, if glibc is installed without the
deprecated sunrpc functionality and libtirpc should replace it.
It's what most distributions use, I believe.
Thanks,
Florian
prev parent reply other threads:[~2022-07-25 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 15:33 Yair Lenga
2022-07-25 15:48 ` Florian Weimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h735p50b.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.org \
--cc=yair.lenga@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).