GNU Dico Manual (split by node): Section: Back: 2. Building the Package Forward: 2.2 Default Server Chapter: FastBack: 2. Building the Package Up: 2. Building the Package FastForward: 3. The dicod daemon. Doc: Contents: Table of Contents Index: Concept Index   ?

2.1 Default Preprocessor

The runtime configuration system uses m4 to preprocess the configuration file (see section Using Preprocessor to Improve the Configuration.), which makes the configuration extremely flexible. We recommend to use GNU m4 as a preprocessor(1). However, any other implementation of m4 may be used. The configure script tries to determine full file name of the preprocessor binary and the necessary command line options. In case it makes a wrong guess, you can instruct it to use a particular preprocessor by using DEFAULT_PREPROCESSOR configuration variable. For example, the following configure invocation instructs it to use /usr/local/bin/gm4:

 
$ ./configure DEFAULT_PREPROCESSOR="/usr/local/bin/gm4 -s"

Note the use of the ‘-s’ preprocessor option. It instructs m4 to produce line directives which help dicod produce correct diagnostics about eventual configuration errors. Unless your m4 implementation does not have this feature, we recommend to always use it in DEFAULT_PREPROCESSOR value.

Finally, if you do not wish to use preprocessor at all, you can disable it using ‘--without-preprocessor’ option to configure.

Footnotes

(1)

http://www.gnu.org/software/m4

This document was generated by Sergey Poznyakoff on July, 7 2010 using texi2html 1.78.

Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.