GCC with -std=c99 complains about not knowing struct timespec

by

Explicitly enabling POSIX features

The timespec comes from POSIX, so you have to ‘enable’ POSIX definitions:

#if __STDC_VERSION__ >= 199901L
#define _XOPEN_SOURCE 600
#else
#define _XOPEN_SOURCE 500
#endif /* __STDC_VERSION__ */

#include <time.h>

void blah(struct timespec asdf)
{
}

int main()
{
    struct timespec asdf;
    return 0;
}

The stanza at the top is what I currently use – it triggers the definitions from Single UNIX Specification (SUS) based on whether you’re using a C99 or C89 compiler.

  • If you want the POSIX 2008 (SUS v4) material, use _XOPEN_SOURCE 700
  • If you want the POSIX 2004 (SUS v3) material, use _XOPEN_SOURCE 600
  • If you want the POSIX 1995 (SUS v2, 1997) material, use _XOPEN_SOURCE 500

As noted in the comments, using _XOPEN_SOURCE strictly enables the XSI (X/Open System Interface) extensions over strict POSIX, but it is very rare for you to want POSIX and not XSI. You should normally specify _XOPEN_SOURCE and not futz with _POSIX_C_SOURCE. See (POSIX 2018) on The Compilation Environment for more information about feature macros.

For my systems in 2010, POSIX 2008 was not as widely available as POSIX 2004, so that’s what I used – but YMMV. Note that SUS v3 and v4 both require C99 compilation. On Solaris, at least, using C89 failed.

GCC provides -std=gnuXX options

If you specify -std=c11 to GCC (or Clang emulating GCC), then only the standard C definitions are enabled. If you use -std=gnu11, then POSIX and other extensions to standard C are visible by default.

Note that GCC 4.x and earlier used -std=gnu90 (corresponding to C90 plus extensions) by default. GCC 5.x and later use -std=gnu11 by default. There was never a version of GCC that enabled -std=gnu99 by default.

Use a header to control the POSIX version information

I now (2019) use a header to encapsulate this information so that future changes only require the change to a single header, not to every source file that uses POSIX features. It was painful editing the old stanza out of multiple source files as time passed and POSIX 2008 became prevalent.

/*
@(#)File:           $RCSfile: posixver.h,v $
@(#)Version:        $Revision: 1.4 $
@(#)Last changed:   $Date: 2017/06/18 00:15:42 $
@(#)Purpose:        Request appropriate POSIX and X/Open Support
@(#)Author:         J Leffler
@(#)Copyright:      (C) JLSS 2010-2017
*/

/*TABSTOP=4*/

#ifndef JLSS_ID_POSIXVER_H
#define JLSS_ID_POSIXVER_H

/*
** Include this file before including system headers.  By default, with
** C99 support from the compiler, it requests POSIX 2008 support.  With
** C89 support only, it requests POSIX 1997 support.  Override the
** default behaviour by setting either _XOPEN_SOURCE or _POSIX_C_SOURCE.
*/

/* _XOPEN_SOURCE 700 is loosely equivalent to _POSIX_C_SOURCE 200809L */
/* _XOPEN_SOURCE 600 is loosely equivalent to _POSIX_C_SOURCE 200112L */
/* _XOPEN_SOURCE 500 is loosely equivalent to _POSIX_C_SOURCE 199506L */

#if !defined(_XOPEN_SOURCE) && !defined(_POSIX_C_SOURCE)
#if defined(__cplusplus)
#define _XOPEN_SOURCE 700   /* SUS v4, POSIX 1003.1 2008/13 (POSIX 2008/13) */
#elif __STDC_VERSION__ >= 199901L
#define _XOPEN_SOURCE 700   /* SUS v4, POSIX 1003.1 2008/13 (POSIX 2008/13) */
#else
#define _XOPEN_SOURCE 500   /* SUS v2, POSIX 1003.1 1997 */
#endif /* __STDC_VERSION__ */
#endif /* !_XOPEN_SOURCE && !_POSIX_C_SOURCE */

#endif /* JLSS_ID_POSIXVER_H */

You may use the information from this header without the attribution and copyright notice normally required by the “CC by-sa 3.0” licence used by Stack Overflow. This code is available in my SOQ (Stack Overflow Questions) repository on GitHub as file posixver.h in the src/libsoq sub-directory.

C11 defines struct timespec

Note that C11 defines struct timespec, and does so in a way that is compatible with POSIX (which defined it first).

The header <time.h> defines the type. Three of the functions that use it are declared in <threads.h> and the other is in <time.h>:

These are also part of C17 (C18) of course. You would have to be compiling with -std=c11 or similar (GCC 9.2.0 seems to recognize both -std=c17 and -std=c18, and -std=c2x for the next version of the standard) for the type struct timespec to be defined automatically.

More Related Contents:

  1. Return value range of the main function
  2. Create statically-linked binary that uses getaddrinfo?
  3. Are prototypes required for all functions in C89, C90 or C99?
  4. Passing a multidimensional variable length array to a function
  5. Tentative definitions in C and linking
  6. Enabling VLAs (variable length arrays) in MS Visual C++?
  7. When should I use mmap for file access?
  8. What is the equivalent to Posix popen() in the Win32 API?
  9. Does printf always flush the buffer on encountering a newline?
  10. What is the difference between C, C99, ANSI C and GNU C?
  11. POSIX API call to list all the pthreads running in a process
  12. Get warning when a variable is shadowed
  13. Are there any platforms where using structure copy on an fd_set (for select() or pselect()) causes problems?
  14. What is the proper #include for the function ‘sleep()’?
  15. How to redirect the output back to the screen after freopen(“out.txt”, “a”, stdout)
  16. Literal string initializer for a character array
  17. Does Microsoft visual studio 2010 support c99?
  18. How to make parent wait for all child processes to finish?
  19. What is the default C -std standard version for the current GCC (especially on Ubuntu)?
  20. Redirect stdout to a file
  21. Why is the fgets function deprecated?
  22. Why was mixing declarations and code forbidden up until C99?
  23. Is int main() { } (without “void”) valid and portable in ISO C?
  24. Is it possible (and safe) to make an accepting socket non-blocking?
  25. Posix regular expression non-greedy
  26. Checking if errno != EINTR: what does it mean?
  27. What’s the difference between “int” and “int_fast16_t”?
  28. How to know if a Linux system call is restartable or not?
  29. Dynamic array allocation on stack in C
  30. Unsigned to signed conversion in C

Leave a Comment