Samuel Thibault <samuel.thiba...@gnu.org> writes: > David Michael, on sam. 06 mai 2017 12:28:51 -0700, wrote: >> The new generated functions all get an additional >> "mach_msg_type_name_t *msgportPoly" parameter and none of the callers >> were updated, so they all fail to compile with "too few arguments" >> errors. > > Indeed, rebuilding glibc gives: > > hurdexec.c:72:29: error: too few arguments to function ‘__proc_task2proc’ > > because client RPC stubs are built by glibc that went unnoticed. > > Do RPC-knowledgeable people know a way to have this change happen in the > server only? Perhaps just using a typedef which will not be the > same in the server and the client?
Whoops. That was me. But tbh, since I only changed out parameters (and obviously the *in* parameters of the async reply part), I don't see why that should change the client stub (as I remarked in the commit message). What did I miss? Can you paste the client code? I still don't see why the out parameter should possibly be polymorphic at the client side, and cannot even imagine what the semantic could be... Justus
signature.asc
Description: PGP signature
