1 .\" Hey Emacs! This file is -*- nroff -*- source.
3 .\" This manpage is Copyright (C) 2006, Michael Kerrisk
5 .\" Permission is granted to make and distribute verbatim copies of this
6 .\" manual provided the copyright notice and this permission notice are
7 .\" preserved on all copies.
9 .\" Permission is granted to copy and distribute modified versions of this
10 .\" manual under the conditions for verbatim copying, provided that the
11 .\" entire resulting derived work is distributed under the terms of a
12 .\" permission notice identical to this one.
14 .\" Since the Linux kernel and libraries are constantly changing, this
15 .\" manual page may be incorrect or out-of-date. The author(s) assume no
16 .\" responsibility for errors or omissions, or for damages resulting from
17 .\" the use of the information contained herein. The author(s) may not
18 .\" have taken the same level of care in the production of this manual,
19 .\" which is licensed free of charge, as they might when working
22 .\" Formatted or processed versions of this manual, if unaccompanied by
23 .\" the source, must acknowledge the copyright and authors of this work.
25 .TH FEATURE_TEST_MACROS 7 2012-01-18 "Linux" "Linux Programmer's Manual"
27 feature_test_macros \- feature test macros
30 .B #include <features.h>
33 Feature test macros allow the programmer to control the definitions that
34 are exposed by system header files when a program is compiled.
37 In order to be effective, a feature test macro
38 .IR "must be defined before including any header files" .
39 This can be done either in the compilation command
40 .RI ( "cc \-DMACRO=value" )
41 or by defining the macro within the source code before
42 including any headers.
44 Some feature test macros are useful for creating portable applications,
45 by preventing nonstandard definitions from being exposed.
46 Other macros can be used to expose nonstandard definitions that
47 are not exposed by default.
48 The precise effects of each of the feature test macros described below
49 can be ascertained by inspecting the
52 .SS Specification of feature test macro requirements in manual pages
53 When a function requires that a feature test macro is defined,
54 the manual page SYNOPSIS typically includes a note of the following form
55 (this example from the
60 .B #include <unistd.h>
62 .BI "int acct(const char *" filename );
66 Feature Test Macro Requirements for glibc (see
67 .BR feature_test_macros (7)):
72 _BSD_SOURCE || (_XOPEN_SOURCE && _XOPEN_SOURCE\ <\ 500)
75 The \fB||\fP means that in order to obtain the declaration of
79 \fIeither\fP of the following macro
80 definitions must be made before including any header files:
85 #define _XOPEN_SOURCE /* or any value < 500 */
89 Alternatively, equivalent definitions can be included in the
95 cc \-D_XOPEN_SOURCE # Or any value < 500
99 Note that, as described below,
100 .BR "some feature test macros are defined by default" ,
101 so that it may not always be necessary to
102 explicitly specify the feature test macro(s) shown in the
105 In a few cases, manual pages use a shorthand for expressing the
106 feature test macro requirements (this example from
111 .B #define _GNU_SOURCE
112 .B #include <fcntl.h>
114 .BI "ssize_t readahead(int " fd ", off64_t *" offset ", size_t " count );
118 This format is employed in cases where only a single
119 feature test macro can be used to expose the function
120 declaration, and that macro is not defined by default.
121 .SS Feature test macros understood by glibc
122 The following paragraphs explain how feature test macros are handled
123 in Linux glibc 2.\fIx\fP, \fIx\fP > 0.
124 .\" The details in glibc 2.0 are simpler, but combining a
125 .\" a description of them with the details in later glibc versions
126 .\" would make for a complicated description.
128 Linux glibc understands the following feature test macros:
132 This macro is implicitly defined by
134 when invoked with, for example, the
141 Defining this macro causes header files to expose definitions as follows:
144 The value 1 exposes definitions conforming to POSIX.1-1990 and
147 The value 2 or greater additionally exposes
148 definitions for POSIX.2-1992.
150 The value 199309L or greater additionally exposes
151 definitions for POSIX.1b (real-time extensions).
152 .\" 199506L functionality is only available since glibc 2.1
154 The value 199506L or greater additionally exposes
155 definitions for POSIX.1c (threads).
158 The value 200112L or greater exposes definitions corresponding
159 to the POSIX.1-2001 base specification (excluding the XSI extension).
162 The value 200809L or greater exposes definitions corresponding
163 to the POSIX.1-2008 base specification (excluding the XSI extension).
167 Defining this obsolete macro with any value is equivalent to defining
172 Defining this macro causes header files to expose definitions as follows:
175 Defining with any value exposes
176 definitions conforming to POSIX.1, POSIX.2, and XPG4.
178 The value 500 or greater additionally exposes
179 definitions for SUSv2 (UNIX 98).
181 (Since glibc 2.2) The value 600 or greater additionally exposes
182 definitions for SUSv3 (UNIX 03; i.e., the POSIX.1-2001 base specification
183 plus the XSI extension) and C99 definitions.
185 (Since glibc 2.10) The value 700 or greater additionally exposes
186 definitions for SUSv4 (i.e., the POSIX.1-2008 base specification
187 plus the XSI extension).
190 .B _XOPEN_SOURCE_EXTENDED
191 If this macro is defined, and
193 is defined, then expose definitions corresponding to the XPG4v2
194 (SUSv1) UNIX extensions (UNIX 95).
195 This macro is also implicitly defined if
197 is defined with a value of 500 or more.
200 Exposes ISO C (1990) Amendment 1 definitions (also known as C95).
201 This macro is recognized since glibc 2.12.
202 The primary change in C95 was support for international character sets.
203 The C95 changes were included in the subsequent C99 standard
207 .BR _ISOC95_SOURCE ).
210 Exposes C99 extensions to ISO C (1990).
211 This macro is recognized since glibc 2.1.3;
212 earlier glibc 2.1.x versions recognized an equivalent macro named
214 (because the C99 standard had not then been finalized).
215 Although the use of the latter macro is obsolete, glibc continues
216 to recognize it for backward compatibility.
219 Exposes declarations consistent with the ISO C11 standard.
220 This macro is recognized since glibc 2.16.
222 .B _LARGEFILE64_SOURCE
223 Expose definitions for the alternative API specified by the
224 LFS (Large File Summit) as a "transitional extension" to the
225 Single UNIX Specification.
226 (See http://opengroup.org/platform/lfs.html.)
227 The alternative API consists of a set of new objects
228 (i.e., functions and types) whose names are suffixed with "64"
237 New programs should not employ this interface; instead
238 .I _FILE_OFFSET_BITS=64
242 Defining this macro with the value 64
243 automatically converts references to 32-bit functions and data types
244 related to file I/O and file system operations into references to
245 their 64-bit counterparts.
246 This is useful for performing I/O on large files (> 2 Gigabytes)
248 (Defining this macro permits correctly written programs to use
249 large files with only a recompilation being required.)
250 64-bit systems naturally permit file sizes greater than 2 Gigabytes,
251 and on those systems this macro has no effect.
254 Defining this macro with any value causes header files to expose
255 BSD-derived definitions.
256 Defining this macro also causes BSD definitions to be preferred in
257 some situations where standards conflict, unless one or more of
260 .BR _POSIX_C_SOURCE ,
262 .BR _XOPEN_SOURCE_EXTENDED ,
265 is defined, in which case BSD definitions are disfavored.
268 Defining this macro with any value causes header files to expose
269 System V-derived definitions.
270 (SVID == System V Interface Definition; see
273 .BR _ATFILE_SOURCE " (since glibc 2.4)"
274 Defining this macro with any value causes header files to expose
275 declarations of a range of functions with the suffix "at";
278 Since glibc 2.10, this macro is also implicitly defined if
280 is defined with a value greater than or equal to 200809L.
283 Defining this macro (with any value) is equivalent to defining
287 .BR _LARGEFILE64_SOURCE ,
289 .BR _XOPEN_SOURCE_EXTENDED ,
292 with the value 200809L
293 (200112L in glibc versions before 2.10;
294 199506L in glibc versions before 2.5;
295 199309L in glibc versions before 2.1)
299 (600 in glibc versions before 2.10;
300 500 in glibc versions before 2.2).
301 In addition, various GNU-specific extensions are also exposed.
302 Where standards conflict, BSD definitions are disfavored.
305 Defining this macro exposes definitions of certain reentrant functions.
306 For multithreaded programs, use
313 provided for compatibility with some other implementations.
315 .BR _FORTIFY_SOURCE " (since glibc 2.3.4)"
316 .\" For more detail, see:
317 .\" http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02055.html
318 .\" [PATCH] Object size checking to prevent (some) buffer overflows
319 .\" * From: Jakub Jelinek <jakub at redhat dot com>
320 .\" * To: gcc-patches at gcc dot gnu dot org
321 .\" * Date: Tue, 21 Sep 2004 04:16:40 -0400
322 Defining this macro causes some lightweight checks to be performed
323 to detect some buffer overflow errors when employing
324 various string and memory manipulation functions.
325 Not all buffer overflows are detected, just some common cases.
326 In the current implementation checks are added for
345 is set to 1, with compiler optimization level 1
347 and above, checks that shouldn't change the behavior of
348 conforming programs are performed.
351 set to 2 some more checking is added, but
352 some conforming programs might fail.
353 Some of the checks can be performed at compile time,
354 and result in compiler warnings;
355 other checks take place at run time,
356 and result in a run-time error if the check fails.
357 Use of this macro requires compiler support, available with
360 .SS Default definitions, implicit definitions, and combining definitions
362 If no feature test macros are explicitly defined,
363 then the following feature test macros are defined by default:
368 .BR _POSIX_C_SOURCE =200809L
369 (200112L in glibc versions before 2.10;
370 199506L in glibc versions before 2.4;
371 199309L in glibc versions before 2.1).
374 .BR __STRICT_ANSI__ ,
377 .BR _POSIX_C_SOURCE ,
379 .BR _XOPEN_SOURCE_EXTENDED ,
383 is explicitly defined, then
387 are not defined by default.
393 are not explicitly defined,
398 is defined with a value of 500 or more, then
402 is defined with the value 1; and
405 is defined with one of the following values:
411 is defined with a value less than 500;
416 is defined with a value greater than or equal to 500 and less than 600;
419 (since glibc 2.4) 200112L,
422 is defined with a value greater than or equal to 600 and less than 700.
428 is defined with a value greater than or equal to 700.
430 Older versions of glibc do not know about the values
431 200112L and 200809L for
432 .BR _POSIX_C_SOURCE ,
433 and the setting of this macro will depend on the glibc version.
437 is undefined, then the setting of
439 depends on the glibc version:
440 199506L, in glibc versions before 2.4;
441 200112L, in glibc 2.4 to 2.9; and
442 200809L, since glibc 2.10.
446 Multiple macros can be defined; the results are additive.
449 .BR _POSIX_C_SOURCE ,
453 .B _XOPEN_SOURCE_EXTENDED
454 was specified by XPG4v2 (aka SUSv1).
457 is not specified by any standard,
458 but is employed on some other implementations.
464 .BR _FORTIFY_SOURCE ,
468 are specific to Linux (glibc).
471 is a Linux/glibc-specific header file.
472 Other systems have an analogous file, but typically with a different name.
473 This header file is automatically included by other header files as
474 required: it is not necessary to explicitly include it in order to
475 employ feature test macros.
477 According to which of the above feature test macros are defined,
479 internally defines various other macros that are checked by
480 other glibc header files.
481 These macros have names prefixed by two underscores (e.g.,
483 Programs should \fInever\fP define these macros directly:
484 instead, the appropriate feature test macro(s) from the
485 list above should be employed.
487 The program below can be used to explore how the various
488 feature test macros are set depending on the glibc version
489 and what feature test macros are explicitly set.
490 The following shell session, on a system with glibc 2.10,
491 shows some examples of what we would see:
497 _POSIX_SOURCE defined
498 _POSIX_C_SOURCE defined: 200809L
501 _ATFILE_SOURCE defined
502 $ \fBcc \-D_XOPEN_SOURCE=500 ftm.c\fP
504 _POSIX_SOURCE defined
505 _POSIX_C_SOURCE defined: 199506L
506 _XOPEN_SOURCE defined: 500
507 $ \fBcc \-D_GNU_SOURCE ftm.c\fP
509 _POSIX_SOURCE defined
510 _POSIX_C_SOURCE defined: 200809L
511 _ISOC99_SOURCE defined
512 _XOPEN_SOURCE defined: 700
513 _XOPEN_SOURCE_EXTENDED defined
514 _LARGEFILE64_SOURCE defined
517 _ATFILE_SOURCE defined
531 main(int argc, char *argv[])
534 printf("_POSIX_SOURCE defined\\n");
537 #ifdef _POSIX_C_SOURCE
538 printf("_POSIX_C_SOURCE defined: %ldL\\n", (long) _POSIX_C_SOURCE);
541 #ifdef _ISOC99_SOURCE
542 printf("_ISOC99_SOURCE defined\\n");
546 printf("_XOPEN_SOURCE defined: %d\\n", _XOPEN_SOURCE);
549 #ifdef _XOPEN_SOURCE_EXTENDED
550 printf("_XOPEN_SOURCE_EXTENDED defined\\n");
553 #ifdef _LARGEFILE64_SOURCE
554 printf("_LARGEFILE64_SOURCE defined\\n");
557 #ifdef _FILE_OFFSET_BITS
558 printf("_FILE_OFFSET_BITS defined: %d\\n", _FILE_OFFSET_BITS);
562 printf("_BSD_SOURCE defined\\n");
566 printf("_SVID_SOURCE defined\\n");
569 #ifdef _ATFILE_SOURCE
570 printf("_ATFILE_SOURCE defined\\n");
574 printf("_GNU_SOURCE defined\\n");
578 printf("_REENTRANT defined\\n");
582 printf("_THREAD_SAFE defined\\n");
585 #ifdef _FORTIFY_SOURCE
586 printf("_FORTIFY_SOURCE defined\\n");
596 The section "Feature Test Macros" under
598 .\" But beware: the info libc document is out of date (Jul 07, mtk)
600 .I /usr/include/features.h