Re: [bug-gnulib] Don't bother checking for unistd.h

2006-01-06 Thread Bruno Haible
_alloc.c, pipe.c, pipe.h, > progreloc.c, wait-process.h: Don't bother checking for unistd.h. For copy-file.c, execute.c, fatal-signal.c, findprog.c, pipe.c, pipe.h, progreloc.c, wait-process.h this is not welcome, because these modules are used in GNU gettext and sometimes people still build GNU gettex

Re: Don't bother checking for unistd.h

2005-10-24 Thread Simon Josefsson
Jim Meyering <[EMAIL PROTECTED]> writes: [unistd.h] > How about adding an accompanying `make check' rule (or similar > mechanism) to help ensure that new/modified .m4 files don't > include that check? Yes, please! I think there is now plenty of stuff gnulib module authors have to think about, th

Re: Don't bother checking for unistd.h

2005-10-24 Thread Jim Meyering
Stepan Kasal <[EMAIL PROTECTED]> wrote: > would the following patch be welcome? > I haven't noticed any of the files in config/srclist.txt. I would welcome it. How about adding an accompanying `make check' rule (or similar mechanism) to help ensure that new/modified .m4 files don't include that

Don't bother checking for unistd.h

2005-10-24 Thread Stepan Kasal
pe.m4, wait-process.m4: Don't bother checking for unistd.h. 2005-10-24 Stepan Kasal <[EMAIL PROTECTED]> * c-stack.c, copy-file.c, execute.c, fatal-signal.c, findprog.c, getlogin_r.c, getlogin_r.h, pagealign_alloc.c, pipe.c, pipe.h, progreloc.c, wait-process.h: