> -Original Message-
> From: Bruno Haible [mailto:br...@clisp.org]
> >
> > From "egrep '^#|timespec' i" ...
> >
> > # 582 "/usr/include/sys/types.h"
> > # 35 "/usr/include/sys/sysmisc.h"
> > typedef struct timespec {
> > } timespec_t;
> > # 35 "/usr/include/sys/siginfo.h"
>
> So? What is yo
> -Original Message-
> From: bug-coreutils-bounces+oss=teragram@gnu.org
> [mailto:bug-coreutils-
> bounces+oss=teragram@gnu.org] On Behalf Of Bruno
> Haible
>
> The usual way to debug this kind of things is
> 1) to look at the preprocessor output. Here:
> $ cc -std -std -I.
Daniel Richard G. wrote:
> I found that adding the following line makes the problem go away:
>
> begin sig2str.c snippet
> #include
>
> #include
> #include < skadoosh
> #include
> #include
> #include
> #include
>
> #include "sig2str.h"
> end sig2str.c snippet
This
Jim Meyering wrote:
> Users expect tools like chmod -R, du and find to work even when run from
> an unreadable directory. Once you impose that requirement, you have
> admitted that save_cwd and restore_cwd are required. With them you must
> admit the possibility of restore_cwd failure. And opena
Sam Steingold wrote:
> How do I figure out if the fd (specifically, stdin=0) is open?
> apparently it is closed when the application is run by nohup.
> the only thing I could figure out so far is fstat: when 0 is open,
> st_mode is 8592, when it is closed it is 8630...
Given that 8592 & 0777 == 06
