So, libio has a call to fcntl, to lock the file currently being read (in share_ctl.c::chare_ctl_next_utts). The problem is, fcntl does not exist in windows; any suggestions on how to get around this (without commenting out the lock, or perhaps writing a compatible lock function).
As far as the unix part goes, do subsequent reads on the locked file cause the locked region to move with the file pointer (i.e. a two byte window from the file pointer)? Or is the point to lock the first two bytes?
--Keith
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, libio has a call to fcntl, to lock the file currently being read (in share_ctl.c::chare_ctl_next_utts). The problem is, fcntl does not exist in windows; any suggestions on how to get around this (without commenting out the lock, or perhaps writing a compatible lock function).
As far as the unix part goes, do subsequent reads on the locked file cause the locked region to move with the file pointer (i.e. a two byte window from the file pointer)? Or is the point to lock the first two bytes?
--Keith