The Exim FAQ

Contents   Previous   Next


Q0101:  I'm having a problem with an Exim RPM.

A0101:  Normally the thing to do if you have a problem with an RPM package is to contact the person who built the package first, not the person who made the software that's in the package. You can usually find out who made a package using the following command:

   rpm --query --package --queryformat '%{PACKAGER}\n' <rpm-package-file>

where <rpm-package-file> is the actual file, e.g. exim-3.03-2.i386.rpm. Or, if the package is installed on your system:

   rpm --query --queryformat '%{PACKAGER}\n' <package-name>

where <package-name> is the name component of the package, e.g. exim. If the packager is unable or unwilling to help, only then should you contact the actual author or associated mailing list of the software.

If you discover through the querying process that you can't tell who the person (or company or group) is who built the package, or that they no longer exist at the given address, then you should reconsider whether you want a package from an unknown source on your system.

If you discover through the querying process that you yourself are the person who built the package, then you should either (a) contact the author or associated mailing list, or (b) reconsider whether you ought to be building and distributing RPM packages of software you don't understand.

Similar rules of thumb govern other binary package formats, including debs, tarballs, and POSIX packages.

Q0102:  I can't get Exim to compile with Berkeley DB version 2.x or 3.x.

A0102:  Have you set "USE_DB=yes" in Local/Makefile? This causes Exim to use the native interface to the DBM library instead of the compatibility interface, which needs a header called ndbm.h that may not exist on your system.

Q0103:  I'm getting an undefined symbol error for hosts_ctl when I try to build Exim. (On some systems this error is undefined reference to 'hosts_ctl'.)

A0103:  You should either remove the definition of USE_TCP_WRAPPERS or add -lwrap to your EXTRALIBS setting in Local/Makefile.

Q0104:  I'm about to upgrade to a new Exim release. Do I need to ensure the spool is empty, or take any other special action?

A0104:  It depends on where you are coming from.

(1)  If you are changing to release 4.00 or later from a release prior to 4.00, you will need to make changes to the run time configuration file. See the file doc/Exim4.upgrade for details. If you are coming from before release 3.00, you should also see doc/Exim3.upgrade.

(2)  If you are upgrading from an Exim 4 release to a later release, you do not need to take special action. New releases are made backwards compatible with old spool files and hints databases, so that upgrading can be done on a running system. All that should be necessary is to install a new binary and then HUP the daemon.

Q0105:  What does the error install-info: command not found mean?

A0105:  You have set INFO_DIRECTORY in your Local/Makefile, and Exim is trying to install the Texinfo documentation, but cannot find the command called install-info. If you have a version of Texinfo prior to 3.9, you should upgrade. Otherwise, check your installation of Texinfo to see why the install-info command is not available.

Q0106:  Exim doesn't seem to be recognizing my operating system type correctly, and so is failing to build.

A0106:  Run the command scripts/os-type -generic. The output should be one of the known OS types, and should correspond to your operating system. You can see which OS are supported by obeying ls OS/Makefile-* and looking at the file name suffixes.

If there is a discrepancy, it means that the script is failing to interpret the output from the uname command correctly, or that the output is wrong. Meanwhile, you can build Exim by obeying

   EXIM_OSTYPE=xxxx make

instead of just make, provided you are running a Bourne-compatible shell, or otherwise by setting EXIM_OSTYPE correctly in your environment. It is probably best to start again from a clean distribution, to avoid any wreckage left over from the failed attempt.

Q0107:  Exim fails to build, complaining about the absence of the killpg function.

A0107:  This function should be present in all modern flavours of Unix. If you are using an older version, you should be able to get round the problem by inserting

   #define killpg(pgid,sig)   kill(-(pgid),sig)

into the file called OS/os.h-xxx, where xxx identifies your operating system, and is the output of the command scripts/os-type -generic.

Q0108:  I'm getting an unresolved symbol ldap_is_ldap_url when trying to build Exim.

A0108:  You must have specified LOOKUP_LDAP=yes in the configuration. Have you remembered to set -lldap somewhere (e.g. in LOOKUP_LIBS)? You need that in order to get the LDAP library scanned when linking.

Q0109:  I'm getting an unresolved symbol mysql_close when trying to build Exim.

A0109:  You must have specified LOOKUP_MYSQL=yes in the configuration. Have you remembered to set -lmysqlclient somewhere (e.g. in LOOKUP_LIBS)? You need that in order to get the MySQL library scanned when linking.

Q0110:  I'm trying to build Exim with PAM support. I have included -lpam in EXTRALIBS, but I'm still getting a linking error:

   /lib/ undefined reference to `dlerror'
   /lib/ undefined reference to `dlclose'
   /lib/ undefined reference to `dlopen'
   /lib/ undefined reference to `dlsym'

A0110:  Add -ldl to EXTRALIBS. In some systems these dynamic loading functions are in their own library.

Q0111:  I'm getting the error db.h: No such file or directory when I try to build Exim.

A0111:  This problem has been seen with RedHat 7.0, but could also happen in other environments. If your system is using the DB3 DBM library, you need to install the DB3 development package in order to build Exim. The package is called something like db3-devel-3.1.14-16.i386.rpm for Linux systems, but you should check which version of DB3 you have installed.

Q0112:  I'm getting the error /usr/bin/ld: cannot find -ldb1 when I try to build Exim.

A0112:  This is probably the same problem as Q0111.

Q0113:  I've compiled Exim and I've managed to start it but there was one problem - it always complained that was not found, even though this file is in /usr/local/lib/mysql/.

A0113:  Solaris: ensure you have this in your Local/Makefile:

   LOOKUP_LIBS=-L/usr/local/lib/mysql -R/usr/local/lib/mysql

Net/Open/FreeBSD: Run this command (or ensure it gets run automatically at boot time):

   ldconfig -m /usr/local/lib/mysql

Linux: add /usr/local/lib/mysql to /etc/ and re-run ldconfig. Alternatively, add

   -Wl,-rpath -Wl,/usr/local/lib/mysql

to EXTRA_LIBS and then re-link (this is similar to the Solaris solution above). This will probably also work on other systems that use GNU Binutils.

Contents   Previous   Next