[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: timespec declaration issue on Tru64

From: Daniel Richard G.
Subject: RE: timespec declaration issue on Tru64
Date: Sun, 14 Dec 2008 19:42:08 -0500

> -----Original Message-----
> From: address@hidden
> [mailto:bug-coreutils-
> address@hidden 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.    -ieee   -g -E sig2str.c >
> i
>      Does this output contain the typedef for 'struct
> timespec' or not?
>      If so, does it use the definition from
> <sys/sysmisc.h> or from gnulib?

>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"

>   2) to try different compiler standard flags. What
> does "cc -std" mean,
>      according to the manual pages? What effect does
> it have to compile
>      without the "-std" option?

-std puts the compiler into relaxed-ANSI mode, instead of the default, which 
is K&R. This flag was actually added by autoconf itself---the build failure I 
quoted was obtained with all *FLAGS variables unset.

(The only other options here are -std1 [strict ANSI], and -ms [Microsoft 
Visual C compatible])


reply via email to

[Prev in Thread] Current Thread [Next in Thread]