On Mon, 14 Jul 2003, Mike Meredith wrote:
> Yes. It's a built-in function with Tru64, but Exim should be remembering
> that Tru64 (or OSF1) has crypt16 built-in but isn't. Adding
> "-DHAVE_CRYPT16" to the CFLAGS line (just above the "HAVE_CRYPT16=yes")
> in OS/Makefile-OSF1 seems to do the trick, although you'll get plenty
> of warnings about it being redefined.
The real bug is that
#include "config.h"
is missing at the start of the crypt16.c module in Exim. This means it
isn't noticing that HAVE_CRYPT16 is set.
Please can one of you with a Tru64 system try adding in the missing line
right at the start of src/crypt16.c in an otherwise vanilla Exim
distribution, and see if it works?
Thanks,
Philip
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
