It is very unlikely that you will ever
have to change the value for it that is predefined in your devtools/OS file. An exception to
this might occur if you need to replace a standard C-library function with one that is
customized to satisfy some local need. For example, consider a replacement for the
syslog(3) routine. First, place a copy of syslog.c in all the source directories. Then, add this
line to your site file:
define(`confOBJADD??, `syslog.o??)
Note that the confOBJADD macro takes the .o form of the object filename, not the source file
name.
If you forget to put a copy of the source in one of the directories, you will see this (or a
similar) error at build-time:
make: Fatal error: Don't know how to make target `syslog.o'
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
94 | Chapter 2: Download, Build, and Install
2.7.48 confOPTIMIZE
How to optimize the compile Build macro
The confOPTIMIZE macro sets the command-line switch that will be passed to the Clanguage
compiler to tune its optimization. This macro assigns a value to the O= Makefile
directive. Normally, it is correctly set for your site in your devtools/OS file.
One reason to change optimization might be to track down a bug that is causing your
installation of sendmail to core-dump. Just add this line to your site file, and re-Build with
-c:
define(`confOPTIMIZE??, `-g??)
The -g switch causes the compiler to produce a binary that can later be debugged with a
symbolic debugger.
Pages:
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192