Postfix: The Definitive Guide

Common Problems

If you run into problems, check the various README files for information about your build. Frequently, they contain information about problems you might run into. Certainly, if there is a README file specific to your platform, be sure to read it. Some possible problems are mentioned below. Exact messages vary depending on your platform and compiler, so the following are general errors similar to what you might see when building Postfix.

Compile Time

No such file or directory

Make sure that the path to your compiler is correct. If you specified a compiler by setting CC when building your Makefile (for example, make makefiles CC="/path“), double-check the path you typed. If the path to your compiler came from the Postfix makedefs file, you might need to override it with:

$ make makefiles CC="/path/to/your/compiler"

Another possibility is to have Postfix call your compiler without a path, assuming its directory is in your environment path:

$ make makefiles CC="cc"

Could not open source file

Make sure that the path to your include files is correct. The include files are normally stored in /usr/include. If your system uses a different path for some reason, you will have to specify it with the -I option set in CCARGS:

$ make makefiles CCARGS="-I/path/to/include"

If you already specified a path with -I double-check your typing.

Unresolved (or undefined) symbol

Make sure that the library paths you specified with the -L option are correct and that you have specified the libraries themselves ...