Bruno Haible [EMAIL PROTECTED] writes:
- Coreutils has a comment explaining why it is useful to compute the
microseconds as
milliseconds * 1000 + 999
rather than as
milliseconds * 1000.
It's useful for that particular case, but there are other cases
where it's not useful
Hi,
The poll module fail under Win32 because of the check for FD_SETSIZE.
Windows use a linear array of sockets (of size FD_SETSIZE). The
descriptor value is not used to address the array.
Attached is a patch that fixe this issue.
Regards,
--
Yoann Vandoorselaere | Responsable RD / CTO |
Paul Eggert wrote:
The practical drawback would be that the --symlink option, in the
coreutils situation, will copy more files and symlink less files.
That's a serious drawback, at least for the way I work. When I
develop, I commonly edit the gnulib copies and expect coreutils to
track
Paul Eggert eggert at CS.UCLA.EDU writes:
The main idea here is that we should try to avoid separate include
files like gettimeofday.h for declarations that POSIX says should be
in a standard file like sys/time.h. Instead, we should patch
sys/time.h by wrapping it; that way the user code
When building coreutils from scratch using make -j3 on a uniprocessor
system, I encountered this failure:
...
mv configmake.h-t configmake.h
mv stdint.h-t stdint.h
test -d sys || mkdir sys
test -d sys || mkdir sys
rm -f sys/stat.h-t sys/stat.h
{ echo '/* DO NOT EDIT! GENERATED
Paul Eggert wrote:
The main idea here is that we should try to avoid separate include
files like gettimeofday.h for declarations that POSIX says should be
in a standard file like sys/time.h. Instead, we should patch
sys/time.h by wrapping it; that way the user code can just code to
the POSIX
Compiling a testdir
- on Linux (to test the case where gettimeofday is present),
- in a cross-compile to Cygwin (to test the case where gettimeofday is
assumed to clobber localtime's buffer),
- in a cross-compile to Mingw (to test the case of missing gettimeofday)
I again come up with
