Hello, On Sat, Sep 11, 2021 at 12:27 PM Joan Lledó <jlle...@mailfence.com> wrote: > Note the additional parameter *mach_msg_type_name_t objectPoly* in > memory_object_create_proxy. I don't know why is it there but I can't > compile the pci arbiter anymore because of that. What can I do?
This is a little change that Samuel has committed recently [0] (at my suggestion). It lets the client specify the "disposition" of the object port(s), i.e. MAKE_SEND, COPY_SEND, or MOVE_SEND. [0]: https://git.savannah.gnu.org/cgit/hurd/gnumach.git/commit/?id=d1c056f2e23b7a9fa91dd5132b040813bfc00487 This doesn't change the RPC format, only the client (user) C routine signature. You'll have to adapt the PCI arbiter code to pass a value for this additional argument. The previous implicit default was MACH_MSG_TYPE_COPY_SEND, so passing it explicitly should be equivalent to the old behavior; but depending on your use case you might find it cleaner to use one of the other two dispositions. Sergey
