1CPP(1) GNU CPP(1)
2
6 cpp - The C Preprocessor
7
9 cpp [-Dmacro[=defn]...] [-Umacro]
10 [-Idir...] [-iquotedir...]
11 [-M|-MM] [-MG] [-MF filename]
12 [-MP] [-MQ target...]
13 [-MT target...]
14 infile [[-o] outfile]
15 Only the most useful options are given above; see below for a more
17 complete list of preprocessor-specific options. In addition, cpp
18 accepts most gcc driver options, which are not listed here. Refer to
19 the GCC documentation for details.
20
22 The C preprocessor, often known as cpp, is a macro processor that is
23 used automatically by the C compiler to transform your program before
24 compilation. It is called a macro processor because it allows you to
25 define macros, which are brief abbreviations for longer constructs.
26 The C preprocessor is intended to be used only with C, C++, and
28 Objective-C source code. In the past, it has been abused as a general
29 text processor. It will choke on input which does not obey C's lexical
30 rules. For example, apostrophes will be interpreted as the beginning
31 of character constants, and cause errors. Also, you cannot rely on it
32 preserving characteristics of the input which are not significant to
33 C-family languages. If a Makefile is preprocessed, all the hard tabs
34 will be removed, and the Makefile will not work.
35 Having said that, you can often get away with using cpp on things which
37 are not C. Other Algol-ish programming languages are often safe (Ada,
38 etc.) So is assembly, with caution. -traditional-cpp mode preserves
39 more white space, and is otherwise more permissive. Many of the
40 problems can be avoided by writing C or C++ style comments instead of
41 native language comments, and keeping macros simple.
42 Wherever possible, you should use a preprocessor geared to the language
44 you are writing in. Modern versions of the GNU assembler have macro
45 facilities. Most high level programming languages have their own
46 conditional compilation and inclusion mechanism. If all else fails,
47 try a true general text processor, such as GNU M4.
48 C preprocessors vary in some details. This manual discusses the GNU C
50 preprocessor, which provides a small superset of the features of ISO
51 Standard C. In its default mode, the GNU C preprocessor does not do a
52 few things required by the standard. These are features which are
53 rarely, if ever, used, and may cause surprising changes to the meaning
54 of a program which does not expect them. To get strict ISO Standard C,
55 you should use the -std=c90, -std=c99, -std=c11 or -std=c17 options,
56 depending on which version of the standard you want. To get all the
57 mandatory diagnostics, you must also use -pedantic.
58 This manual describes the behavior of the ISO preprocessor. To
60 minimize gratuitous differences, where the ISO preprocessor's behavior
61 does not conflict with traditional semantics, the traditional
62 preprocessor should behave the same way. The various differences that
63 do exist are detailed in the section Traditional Mode.
64 For clarity, unless noted otherwise, references to CPP in this manual
66 refer to GNU CPP.
67
69 The cpp command expects two file names as arguments, infile and
70 outfile. The preprocessor reads infile together with any other files
71 it specifies with #include. All the output generated by the combined
72 input files is written in outfile.
73 Either infile or outfile may be -, which as infile means to read from
75 standard input and as outfile means to write to standard output. If
76 either file is omitted, it means the same as if - had been specified
77 for that file. You can also use the -o outfile option to specify the
78 output file.
79 Unless otherwise noted, or the option ends in =, all options which take
81 an argument may have that argument appear either immediately after the
82 option, or with a space between option and argument: -Ifoo and -I foo
83 have the same effect.
84 Many options have multi-letter names; therefore multiple single-letter
86 options may not be grouped: -dM is very different from -d -M.
87 -D name
89 Predefine name as a macro, with definition 1.
90 -D name=definition
92 The contents of definition are tokenized and processed as if they
93 appeared during translation phase three in a #define directive. In
94 particular, the definition is truncated by embedded newline
95 characters.
96 If you are invoking the preprocessor from a shell or shell-like
98 program you may need to use the shell's quoting syntax to protect
99 characters such as spaces that have a meaning in the shell syntax.
100 If you wish to define a function-like macro on the command line,
102 write its argument list with surrounding parentheses before the
103 equals sign (if any). Parentheses are meaningful to most shells,
104 so you should quote the option. With sh and csh,
105 -D'name(args...)=definition' works.
106 -D and -U options are processed in the order they are given on the
108 command line. All -imacros file and -include file options are
109 processed after all -D and -U options.
110 -U name
112 Cancel any previous definition of name, either built in or provided
113 with a -D option.
114 -include file
116 Process file as if "#include "file"" appeared as the first line of
117 the primary source file. However, the first directory searched for
118 file is the preprocessor's working directory instead of the
119 directory containing the main source file. If not found there, it
120 is searched for in the remainder of the "#include "..."" search
121 chain as normal.
122 If multiple -include options are given, the files are included in
124 the order they appear on the command line.
125 -imacros file
127 Exactly like -include, except that any output produced by scanning
128 file is thrown away. Macros it defines remain defined. This
129 allows you to acquire all the macros from a header without also
130 processing its declarations.
131 All files specified by -imacros are processed before all files
133 specified by -include.
134 -undef
136 Do not predefine any system-specific or GCC-specific macros. The
137 standard predefined macros remain defined.
138 -pthread
140 Define additional macros required for using the POSIX threads
141 library. You should use this option consistently for both
142 compilation and linking. This option is supported on GNU/Linux
143 targets, most other Unix derivatives, and also on x86 Cygwin and
144 MinGW targets.
145 -M Instead of outputting the result of preprocessing, output a rule
147 suitable for make describing the dependencies of the main source
148 file. The preprocessor outputs one make rule containing the object
149 file name for that source file, a colon, and the names of all the
150 included files, including those coming from -include or -imacros
151 command-line options.
152 Unless specified explicitly (with -MT or -MQ), the object file name
154 consists of the name of the source file with any suffix replaced
155 with object file suffix and with any leading directory parts
156 removed. If there are many included files then the rule is split
157 into several lines using \-newline. The rule has no commands.
158 This option does not suppress the preprocessor's debug output, such
160 as -dM. To avoid mixing such debug output with the dependency
161 rules you should explicitly specify the dependency output file with
162 -MF, or use an environment variable like DEPENDENCIES_OUTPUT.
163 Debug output is still sent to the regular output stream as normal.
164 Passing -M to the driver implies -E, and suppresses warnings with
166 an implicit -w.
167 -MM Like -M but do not mention header files that are found in system
169 header directories, nor header files that are included, directly or
170 indirectly, from such a header.
171 This implies that the choice of angle brackets or double quotes in
173 an #include directive does not in itself determine whether that
174 header appears in -MM dependency output.
175 -MF file
177 When used with -M or -MM, specifies a file to write the
178 dependencies to. If no -MF switch is given the preprocessor sends
179 the rules to the same place it would send preprocessed output.
180 When used with the driver options -MD or -MMD, -MF overrides the
182 default dependency output file.
183 If file is -, then the dependencies are written to stdout.
185 -MG In conjunction with an option such as -M requesting dependency
187 generation, -MG assumes missing header files are generated files
188 and adds them to the dependency list without raising an error. The
189 dependency filename is taken directly from the "#include" directive
190 without prepending any path. -MG also suppresses preprocessed
191 output, as a missing header file renders this useless.
192 This feature is used in automatic updating of makefiles.
194 -MP This option instructs CPP to add a phony target for each dependency
196 other than the main file, causing each to depend on nothing. These
197 dummy rules work around errors make gives if you remove header
198 files without updating the Makefile to match.
199 This is typical output:
201 test.o: test.c test.h
203 test.h:
205 -MT target
207 Change the target of the rule emitted by dependency generation. By
208 default CPP takes the name of the main input file, deletes any
209 directory components and any file suffix such as .c, and appends
210 the platform's usual object suffix. The result is the target.
211 An -MT option sets the target to be exactly the string you specify.
213 If you want multiple targets, you can specify them as a single
214 argument to -MT, or use multiple -MT options.
215 For example, -MT '$(objpfx)foo.o' might give
217 $(objpfx)foo.o: foo.c
219 -MQ target
221 Same as -MT, but it quotes any characters which are special to
222 Make. -MQ '$(objpfx)foo.o' gives
223 $$(objpfx)foo.o: foo.c
225 The default target is automatically quoted, as if it were given
227 with -MQ.
228 -MD -MD is equivalent to -M -MF file, except that -E is not implied.
230 The driver determines file based on whether an -o option is given.
231 If it is, the driver uses its argument but with a suffix of .d,
232 otherwise it takes the name of the input file, removes any
233 directory components and suffix, and applies a .d suffix.
234 If -MD is used in conjunction with -E, any -o switch is understood
236 to specify the dependency output file, but if used without -E, each
237 -o is understood to specify a target object file.
238 Since -E is not implied, -MD can be used to generate a dependency
240 output file as a side effect of the compilation process.
241 -MMD
243 Like -MD except mention only user header files, not system header
244 files.
245 -fpreprocessed
247 Indicate to the preprocessor that the input file has already been
248 preprocessed. This suppresses things like macro expansion,
249 trigraph conversion, escaped newline splicing, and processing of
250 most directives. The preprocessor still recognizes and removes
251 comments, so that you can pass a file preprocessed with -C to the
252 compiler without problems. In this mode the integrated
253 preprocessor is little more than a tokenizer for the front ends.
254 -fpreprocessed is implicit if the input file has one of the
256 extensions .i, .ii or .mi. These are the extensions that GCC uses
257 for preprocessed files created by -save-temps.
258 -fdirectives-only
260 When preprocessing, handle directives, but do not expand macros.
261 The option's behavior depends on the -E and -fpreprocessed options.
263 With -E, preprocessing is limited to the handling of directives
265 such as "#define", "#ifdef", and "#error". Other preprocessor
266 operations, such as macro expansion and trigraph conversion are not
267 performed. In addition, the -dD option is implicitly enabled.
268 With -fpreprocessed, predefinition of command line and most builtin
270 macros is disabled. Macros such as "__LINE__", which are
271 contextually dependent, are handled normally. This enables
272 compilation of files previously preprocessed with "-E
273 -fdirectives-only".
274 With both -E and -fpreprocessed, the rules for -fpreprocessed take
276 precedence. This enables full preprocessing of files previously
277 preprocessed with "-E -fdirectives-only".
278 -fdollars-in-identifiers
280 Accept $ in identifiers.
281 -fextended-identifiers
283 Accept universal character names in identifiers. This option is
284 enabled by default for C99 (and later C standard versions) and C++.
285 -fno-canonical-system-headers
287 When preprocessing, do not shorten system header paths with
288 canonicalization.
289 -ftabstop=width
291 Set the distance between tab stops. This helps the preprocessor
292 report correct column numbers in warnings or errors, even if tabs
293 appear on the line. If the value is less than 1 or greater than
294 100, the option is ignored. The default is 8.
295 -ftrack-macro-expansion[=level]
297 Track locations of tokens across macro expansions. This allows the
298 compiler to emit diagnostic about the current macro expansion stack
299 when a compilation error occurs in a macro expansion. Using this
300 option makes the preprocessor and the compiler consume more memory.
301 The level parameter can be used to choose the level of precision of
302 token location tracking thus decreasing the memory consumption if
303 necessary. Value 0 of level de-activates this option. Value 1
304 tracks tokens locations in a degraded mode for the sake of minimal
305 memory overhead. In this mode all tokens resulting from the
306 expansion of an argument of a function-like macro have the same
307 location. Value 2 tracks tokens locations completely. This value is
308 the most memory hungry. When this option is given no argument, the
309 default parameter value is 2.
310 Note that "-ftrack-macro-expansion=2" is activated by default.
312 -fmacro-prefix-map=old=new
314 When preprocessing files residing in directory old, expand the
315 "__FILE__" and "__BASE_FILE__" macros as if the files resided in
316 directory new instead. This can be used to change an absolute path
317 to a relative path by using . for new which can result in more
318 reproducible builds that are location independent. This option
319 also affects "__builtin_FILE()" during compilation. See also
320 -ffile-prefix-map.
321 -fexec-charset=charset
323 Set the execution character set, used for string and character
324 constants. The default is UTF-8. charset can be any encoding
325 supported by the system's "iconv" library routine.
326 -fwide-exec-charset=charset
328 Set the wide execution character set, used for wide string and
329 character constants. The default is UTF-32 or UTF-16, whichever
330 corresponds to the width of "wchar_t". As with -fexec-charset,
331 charset can be any encoding supported by the system's "iconv"
332 library routine; however, you will have problems with encodings
333 that do not fit exactly in "wchar_t".
334 -finput-charset=charset
336 Set the input character set, used for translation from the
337 character set of the input file to the source character set used by
338 GCC. If the locale does not specify, or GCC cannot get this
339 information from the locale, the default is UTF-8. This can be
340 overridden by either the locale or this command-line option.
341 Currently the command-line option takes precedence if there's a
342 conflict. charset can be any encoding supported by the system's
343 "iconv" library routine.
344 -fworking-directory
346 Enable generation of linemarkers in the preprocessor output that
347 let the compiler know the current working directory at the time of
348 preprocessing. When this option is enabled, the preprocessor
349 emits, after the initial linemarker, a second linemarker with the
350 current working directory followed by two slashes. GCC uses this
351 directory, when it's present in the preprocessed input, as the
352 directory emitted as the current working directory in some
353 debugging information formats. This option is implicitly enabled
354 if debugging information is enabled, but this can be inhibited with
355 the negated form -fno-working-directory. If the -P flag is present
356 in the command line, this option has no effect, since no "#line"
357 directives are emitted whatsoever.
358 -A predicate=answer
360 Make an assertion with the predicate predicate and answer answer.
361 This form is preferred to the older form -A predicate(answer),
362 which is still supported, because it does not use shell special
363 characters.
364 -A -predicate=answer
366 Cancel an assertion with the predicate predicate and answer answer.
367 -C Do not discard comments. All comments are passed through to the
369 output file, except for comments in processed directives, which are
370 deleted along with the directive.
371 You should be prepared for side effects when using -C; it causes
373 the preprocessor to treat comments as tokens in their own right.
374 For example, comments appearing at the start of what would be a
375 directive line have the effect of turning that line into an
376 ordinary source line, since the first token on the line is no
377 longer a #.
378 -CC Do not discard comments, including during macro expansion. This is
380 like -C, except that comments contained within macros are also
381 passed through to the output file where the macro is expanded.
382 In addition to the side effects of the -C option, the -CC option
384 causes all C++-style comments inside a macro to be converted to
385 C-style comments. This is to prevent later use of that macro from
386 inadvertently commenting out the remainder of the source line.
387 The -CC option is generally used to support lint comments.
389 -P Inhibit generation of linemarkers in the output from the
391 preprocessor. This might be useful when running the preprocessor
392 on something that is not C code, and will be sent to a program
393 which might be confused by the linemarkers.
394 -traditional
396 -traditional-cpp
397 Try to imitate the behavior of pre-standard C preprocessors, as
398 opposed to ISO C preprocessors.
399 Note that GCC does not otherwise attempt to emulate a pre-standard
401 C compiler, and these options are only supported with the -E
402 switch, or when invoking CPP explicitly.
403 -trigraphs
405 Support ISO C trigraphs. These are three-character sequences, all
406 starting with ??, that are defined by ISO C to stand for single
407 characters. For example, ??/ stands for \, so '??/n' is a
408 character constant for a newline.
409 By default, GCC ignores trigraphs, but in standard-conforming modes
411 it converts them. See the -std and -ansi options.
412 -remap
414 Enable special code to work around file systems which only permit
415 very short file names, such as MS-DOS.
416 -H Print the name of each header file used, in addition to other
418 normal activities. Each name is indented to show how deep in the
419 #include stack it is. Precompiled header files are also printed,
420 even if they are found to be invalid; an invalid precompiled header
421 file is printed with ...x and a valid one with ...! .
422 -dletters
424 Says to make debugging dumps during compilation as specified by
425 letters. The flags documented here are those relevant to the
426 preprocessor. Other letters are interpreted by the compiler
427 proper, or reserved for future versions of GCC, and so are silently
428 ignored. If you specify letters whose behavior conflicts, the
429 result is undefined.
430 -dM Instead of the normal output, generate a list of #define
432 directives for all the macros defined during the execution of
433 the preprocessor, including predefined macros. This gives you
434 a way of finding out what is predefined in your version of the
435 preprocessor. Assuming you have no file foo.h, the command
436 touch foo.h; cpp -dM foo.h
438 shows all the predefined macros.
440 -dD Like -dM except in two respects: it does not include the
442 predefined macros, and it outputs both the #define directives
443 and the result of preprocessing. Both kinds of output go to
444 the standard output file.
445 -dN Like -dD, but emit only the macro names, not their expansions.
447 -dI Output #include directives in addition to the result of
449 preprocessing.
450 -dU Like -dD except that only macros that are expanded, or whose
452 definedness is tested in preprocessor directives, are output;
453 the output is delayed until the use or test of the macro; and
454 #undef directives are also output for macros tested but
455 undefined at the time.
456 -fdebug-cpp
458 This option is only useful for debugging GCC. When used from CPP
459 or with -E, it dumps debugging information about location maps.
460 Every token in the output is preceded by the dump of the map its
461 location belongs to.
462 When used from GCC without -E, this option has no effect.
464 -I dir
466 -iquote dir
467 -isystem dir
468 -idirafter dir
469 Add the directory dir to the list of directories to be searched for
470 header files during preprocessing.
471 If dir begins with = or $SYSROOT, then the = or $SYSROOT is
473 replaced by the sysroot prefix; see --sysroot and -isysroot.
474 Directories specified with -iquote apply only to the quote form of
476 the directive, "#include "file"". Directories specified with -I,
477 -isystem, or -idirafter apply to lookup for both the
478 "#include "file"" and "#include <file>" directives.
479 You can specify any number or combination of these options on the
481 command line to search for header files in several directories.
482 The lookup order is as follows:
483 1. For the quote form of the include directive, the directory of
485 the current file is searched first.
486 2. For the quote form of the include directive, the directories
488 specified by -iquote options are searched in left-to-right
489 order, as they appear on the command line.
490 3. Directories specified with -I options are scanned in left-to-
492 right order.
493 4. Directories specified with -isystem options are scanned in
495 left-to-right order.
496 5. Standard system directories are scanned.
498 6. Directories specified with -idirafter options are scanned in
500 left-to-right order.
501 You can use -I to override a system header file, substituting your
503 own version, since these directories are searched before the
504 standard system header file directories. However, you should not
505 use this option to add directories that contain vendor-supplied
506 system header files; use -isystem for that.
507 The -isystem and -idirafter options also mark the directory as a
509 system directory, so that it gets the same special treatment that
510 is applied to the standard system directories.
511 If a standard system include directory, or a directory specified
513 with -isystem, is also specified with -I, the -I option is ignored.
514 The directory is still searched but as a system directory at its
515 normal position in the system include chain. This is to ensure
516 that GCC's procedure to fix buggy system headers and the ordering
517 for the "#include_next" directive are not inadvertently changed.
518 If you really need to change the search order for system
519 directories, use the -nostdinc and/or -isystem options.
520 -I- Split the include path. This option has been deprecated. Please
522 use -iquote instead for -I directories before the -I- and remove
523 the -I- option.
524 Any directories specified with -I options before -I- are searched
526 only for headers requested with "#include "file""; they are not
527 searched for "#include <file>". If additional directories are
528 specified with -I options after the -I-, those directories are
529 searched for all #include directives.
530 In addition, -I- inhibits the use of the directory of the current
532 file directory as the first search directory for "#include "file"".
533 There is no way to override this effect of -I-.
534 -iprefix prefix
536 Specify prefix as the prefix for subsequent -iwithprefix options.
537 If the prefix represents a directory, you should include the final
538 /.
539 -iwithprefix dir
541 -iwithprefixbefore dir
542 Append dir to the prefix specified previously with -iprefix, and
543 add the resulting directory to the include search path.
544 -iwithprefixbefore puts it in the same place -I would; -iwithprefix
545 puts it where -idirafter would.
546 -isysroot dir
548 This option is like the --sysroot option, but applies only to
549 header files (except for Darwin targets, where it applies to both
550 header files and libraries). See the --sysroot option for more
551 information.
552 -imultilib dir
554 Use dir as a subdirectory of the directory containing target-
555 specific C++ headers.
556 -nostdinc
558 Do not search the standard system directories for header files.
559 Only the directories explicitly specified with -I, -iquote,
560 -isystem, and/or -idirafter options (and the directory of the
561 current file, if appropriate) are searched.
562 -nostdinc++
564 Do not search for header files in the C++-specific standard
565 directories, but do still search the other standard directories.
566 (This option is used when building the C++ library.)
567 -Wcomment
569 -Wcomments
570 Warn whenever a comment-start sequence /* appears in a /* comment,
571 or whenever a backslash-newline appears in a // comment. This
572 warning is enabled by -Wall.
573 -Wtrigraphs
575 Warn if any trigraphs are encountered that might change the meaning
576 of the program. Trigraphs within comments are not warned about,
577 except those that would form escaped newlines.
578 This option is implied by -Wall. If -Wall is not given, this
580 option is still enabled unless trigraphs are enabled. To get
581 trigraph conversion without warnings, but get the other -Wall
582 warnings, use -trigraphs -Wall -Wno-trigraphs.
583 -Wundef
585 Warn if an undefined identifier is evaluated in an "#if" directive.
586 Such identifiers are replaced with zero.
587 -Wexpansion-to-defined
589 Warn whenever defined is encountered in the expansion of a macro
590 (including the case where the macro is expanded by an #if
591 directive). Such usage is not portable. This warning is also
592 enabled by -Wpedantic and -Wextra.
593 -Wunused-macros
595 Warn about macros defined in the main file that are unused. A
596 macro is used if it is expanded or tested for existence at least
597 once. The preprocessor also warns if the macro has not been used
598 at the time it is redefined or undefined.
599 Built-in macros, macros defined on the command line, and macros
601 defined in include files are not warned about.
602 Note: If a macro is actually used, but only used in skipped
604 conditional blocks, then the preprocessor reports it as unused. To
605 avoid the warning in such a case, you might improve the scope of
606 the macro's definition by, for example, moving it into the first
607 skipped block. Alternatively, you could provide a dummy use with
608 something like:
609 #if defined the_macro_causing_the_warning
611 #endif
612 -Wno-endif-labels
614 Do not warn whenever an "#else" or an "#endif" are followed by
615 text. This sometimes happens in older programs with code of the
616 form
617 #if FOO
619 ...
620 #else FOO
621 ...
622 #endif FOO
623 The second and third "FOO" should be in comments. This warning is
625 on by default.
626
628 This section describes the environment variables that affect how CPP
629 operates. You can use them to specify directories or prefixes to use
630 when searching for include files, or to control dependency output.
631 Note that you can also specify places to search using options such as
633 -I, and control dependency output with options like -M. These take
634 precedence over environment variables, which in turn take precedence
635 over the configuration of GCC.
636 CPATH
638 C_INCLUDE_PATH
639 CPLUS_INCLUDE_PATH
640 OBJC_INCLUDE_PATH
641 Each variable's value is a list of directories separated by a
642 special character, much like PATH, in which to look for header
643 files. The special character, "PATH_SEPARATOR", is target-
644 dependent and determined at GCC build time. For Microsoft Windows-
645 based targets it is a semicolon, and for almost all other targets
646 it is a colon.
647 CPATH specifies a list of directories to be searched as if
649 specified with -I, but after any paths given with -I options on the
650 command line. This environment variable is used regardless of
651 which language is being preprocessed.
652 The remaining environment variables apply only when preprocessing
654 the particular language indicated. Each specifies a list of
655 directories to be searched as if specified with -isystem, but after
656 any paths given with -isystem options on the command line.
657 In all these variables, an empty element instructs the compiler to
659 search its current working directory. Empty elements can appear at
660 the beginning or end of a path. For instance, if the value of
661 CPATH is ":/special/include", that has the same effect as
662 -I. -I/special/include.
663 DEPENDENCIES_OUTPUT
665 If this variable is set, its value specifies how to output
666 dependencies for Make based on the non-system header files
667 processed by the compiler. System header files are ignored in the
668 dependency output.
669 The value of DEPENDENCIES_OUTPUT can be just a file name, in which
671 case the Make rules are written to that file, guessing the target
672 name from the source file name. Or the value can have the form
673 file target, in which case the rules are written to file file using
674 target as the target name.
675 In other words, this environment variable is equivalent to
677 combining the options -MM and -MF, with an optional -MT switch too.
678 SUNPRO_DEPENDENCIES
680 This variable is the same as DEPENDENCIES_OUTPUT (see above),
681 except that system header files are not ignored, so it implies -M
682 rather than -MM. However, the dependence on the main input file is
683 omitted.
684 SOURCE_DATE_EPOCH
686 If this variable is set, its value specifies a UNIX timestamp to be
687 used in replacement of the current date and time in the "__DATE__"
688 and "__TIME__" macros, so that the embedded timestamps become
689 reproducible.
690 The value of SOURCE_DATE_EPOCH must be a UNIX timestamp, defined as
692 the number of seconds (excluding leap seconds) since 01 Jan 1970
693 00:00:00 represented in ASCII; identical to the output of
694 @command{date +%s} on GNU/Linux and other systems that support the
695 %s extension in the "date" command.
696 The value should be a known timestamp such as the last modification
698 time of the source or package and it should be set by the build
699 process.
700
702 gpl(7), gfdl(7), fsf-funding(7), gcc(1), and the Info entries for cpp
703 and gcc.
704
706 Copyright (c) 1987-2019 Free Software Foundation, Inc.
707 Permission is granted to copy, distribute and/or modify this document
709 under the terms of the GNU Free Documentation License, Version 1.3 or
710 any later version published by the Free Software Foundation. A copy of
711 the license is included in the man page gfdl(7). This manual contains
712 no Invariant Sections. The Front-Cover Texts are (a) (see below), and
713 the Back-Cover Texts are (b) (see below).
714 (a) The FSF's Front-Cover Text is:
716 A GNU Manual
718 (b) The FSF's Back-Cover Text is:
720 You have freedom to copy and modify this GNU Manual, like GNU
722 software. Copies published by the Free Software Foundation raise
723 funds for GNU development.
724gcc-9.2.1 2019-08-27 CPP(1)