Re: need opendir_safer, dirent--.h

2009-09-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 9/2/2009 1:00 PM: > And here's openat-safer, plus a rework of making fts safer. Well, if I wouldn't create compilation errors in the process. > + * lib/chdir-long.c (includes): Use "fcntl--.h", since openat > + emul

bootstrap: improve find_tool

2009-09-03 Thread Akim Demaille
Hi Friends, This makes Bison's and gnulib's bootstraps more alike. Cheers, Akim 0001-bootstrap-improve-error-message.patch Description: Binary data

Re: make openat declarations consistent

2009-09-03 Thread Eric Blake
Eric Blake byu.net> writes: > > That brings up the lack of an faccessat replacement in gnulib. > > I'll post a module for this shortly. It is feasible for a system to have faccessat but not euidaccess (if they are complying strictly with POSIX 2008), so we might as well add that to our euidac

Re: make openat declarations consistent

2009-09-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 9/3/2009 6:52 AM: > I'm adjusting it to use faccessat with AT_EACCESS instead. Ouch. Cygwin 1.7 has faccessat but not euidaccess, and it currently has bugs (including no AT_EACCESS support, even though AT_EACCESS is defin

Re: fts: slightly more robust

2009-09-03 Thread Jim Meyering
Eric Blake wrote: > Eric Blake byu.net> writes: >> Here's the latest draft of my patch. > > While we're at it, I noticed via findutils that fts leaks fds into child > processes. This plugs the fts leak (but completely fixing find also requires > a > patch to findutils). > > Hmm - POSIX states th

Re: make openat declarations consistent

2009-09-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 9/3/2009 6:52 AM: > But in the long run, we should provide a replacement function, > as we do for all other *at functions. In the *at family, gnulib is still missing: faccessat linkat mknodat mkfifoat readlinkat renameat

Re: make openat declarations consistent

2009-09-03 Thread Jim Meyering
Eric Blake wrote: > Jim, what do you think of this patch, making it possible to avoid > including "openat.h" if you only use the POSIX 2008 interfaces? That's definitely the right thing to do. Thanks for working on this. I haven't looked at it carefully yet, but already your mention of AT_EACCESS

make openat declarations consistent

2009-09-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim, what do you think of this patch, making it possible to avoid including "openat.h" if you only use the POSIX 2008 interfaces? - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -BEGIN PGP SIGNATURE--

Re: avoiding obsolete macros like AC_TRY_RUN

2009-09-03 Thread Paolo Bonzini
Drawbacks of AC_*_IFELSE: - Unmnemonic naming of the macros. Macros and procedure names should follow the convention of "verb" or "verb_noun", so that they can better be remembered by people who are familiar with English grammar. Well, the common name was already taken