The ENVDEF= directive is
primarily used to specify code that should be specially included or excluded when
compiling. The following example shows support for identd(8) being excluded from the
compiled binary of sendmail:*
APPENDDEF(`conf_sendmail_ENVDEF??, `-DIDENTPROTO=0??)
Note that conf_prog_ENVDEF is often given values in the devtools/OS file for your architecture.
To avoid clobbering those values, use APPENDDEF to define conf_prog_ENVDEF.
To use the conf_prog_ENVDEF macro, simply replace the ???prog??? with the name of any of the
programs or library directories in the sendmail source tree. For example, conf_vacation_
ENVDEF is used withth e vacation program, and conf_mail_local_ENVDEF?? is used withth e
mail.local program.
When a single macro is needed to affect all programs, you can use the confENVDEF macro:
APPENDDEF(`confENVDEF??, `-DNISPLUS=1??)
* Note that, once excluded, support cannot easily be included later by using options. It might be better to turn
some facilities, suchas identd(8), off and on with options rather than compiling them out. See ?§24.9.119.13
on page 1104 for a description of the Timeout.ident option.
?? Th eBuild script magically changes the dot into an underscore to keep m4 from complaining.
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
Pages:
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159