glibc/libtirpc and future of client RPC code
Thorsten Kukuk
kukuk@suse.de
Mon Jul 6 12:31:00 GMT 2015
On Thu, Jun 25, Mike Frysinger wrote:
> pretty sure the --disable-obsolete-rpc flag already accomplishes this. the
> problem is that libtirpc is not a full replacement yet for the API in glibc.
Yes, I learned that now, too, even after fixing some functions
and adding missing compat functions, there are still quite a lot
of small, but important changes. Especially the naming of variables
in structs :(
Is there somewhere a list or something similar with the biggest problems
found out when tryint to disable sunrpc in glibc by default?
With my latest TI-RPC patches, I only see two remaining problems,
both not solveable and needs adjustement in the applications:
1. programs trying to hook into svc_run().
2. different naming of some variables.
The later may be solveable with some defines.
Thorsten
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
More information about the Libc-alpha
mailing list