[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: [PATCH hurd 1/6] Add file record locking support: libfshelp_rlo

From: Samuel Thibault
Subject: Re: RFC: [PATCH hurd 1/6] Add file record locking support: libfshelp_rlock.patch
Date: Sat, 8 Dec 2018 01:20:08 +0100
User-agent: NeoMutt/20170113 (1.7.2)

Svante Signell, le sam. 08 déc. 2018 01:14:34 +0100, a ecrit:
> On Mon, 2018-12-03 at 12:17 +0100, Samuel Thibault wrote:
> > Samuel Thibault, le lun. 03 déc. 2018 12:14:42 +0100, a ecrit:
> > > to which you'd pass MACH_PORT_NULL for now.  And in the server, in the
> > > GETLK case, set the l_pid field to -1 for now.
> > 
> > More precisely: in the server, for now set the field to -1 if the port
> > is null, and return EOPNOTSUPP if the port is not null.
> Hi again,
> A few questions:
> When building Hurd with updated RPC for file_record_lock (before updating the
> RPCfile), i.e. libdiskfs/file-record-lock.c et al I have to exclude the 
> includes
> of the *fs_S.h, since glibc is not updated yet. What to do?

You can just install the defs file from the hurd repo, then build glibc
to get the RPC headers, then build the hurd repo.

> Additionally when building the files in libfshelp-tests I have to add another
> argument to the file_record_lock call when including fs_U.h:
> mach_msg_type_name_t rendezvousPoly.

Well, yes, just like io_reauthenticate etc., you'll set


reply via email to

[Prev in Thread] Current Thread [Next in Thread]