Storage size of timespec isn't known

c linux gnu c99 timespec
grizzle picture grizzle · Mar 4, 2017 · Viewed 7.8k times · Source

I have seen this solution but I am getting the same errors. For a class, we had to switch to the c99 compiler instead of gnu but now timespec seems to be broken. Along with "storage size of timespec isn't known", I am getting a bunch of other errors like "CLOCK_MONOTONIC undeclared", "dereferencing a pointer to incomplete type 'struct timespec'", and unused variable warnings but I assume these would go away once I work out the compiler issue.

I wouldn't imagine there is anything wrong with the way I am declaring timespec variables,

struct timespec startTime;

Answer

alk picture alk · Mar 5, 2017

As this kind of "clock" support isn't C99 but POSIX, it's not enabled by default.

To enable it you want to pass the option -D_POSIX_C_SOURCE=199309L to the compiler or put a 

#define _POSIX_C_SOURCE 199309L

at very beginning of the source file(s) in question.

See also man clock_gettime for reference.

Related questions

Convert milliseconds to timespec for GNU port

I want to convert milliseconds into timespec structure used by GNU Linux. I have tried following code for the same. timespec GetTimeSpecValue(unsigned long milisec) { struct timespec req; //long sec = (milisecondtime /1000); time_t sec = (time_t)(milisec/1000); req->tv_…

Read More
Seeking and reading large files in a Linux C++ application

I am running into integer overflow using the standard ftell and fseek options inside of G++, but I guess I was mistaken because it seems that ftell64 and fseek64 are not available. I have been searching and many websites seem …

Read More
Invoking GCC as "cc" versus "gcc"

I am aware that on most GNU/Linux systems, GCC can be invoked by the name "cc" from the command line (as opposed to "gcc"). Is there any difference in GCC's behavior when it is invoked one way versus the …

Read More