According to manu@...:
>
> > a change of line 7386 in configure from
> >
> > if test "${enable_drac+set}" = set; then
> >
> > to
> >
> > if test $enable_drac = yes; then
> >
> > would solve this problem for me ...
>
> Anyone understands the problem and can provide a patch against
> configure.ac ?
basically, the test '"${enable_drac+set}" = set' just
checks if either --enable-drac or --disable-drac were used.
Then, it assigns CFLAGS inconditionnaly, it's wrong.
Same problem for --enable-dnsrbl, less visible.
Try that:
--- configure.ac.orig 2006-08-20 21:38:26.000000000 +0200
+++ configure.ac 2006-08-20 21:40:14.000000000 +0200
@@ -327,7 +327,9 @@
# Check for DRAC
AC_ARG_ENABLE(drac,
[ --enable-drac Enable DRAC support],
- [CFLAGS=$CFLAGS" -DUSE_DRAC"])
+ [if test x$enableval = xyes; then
+ CFLAGS=$CFLAGS" -DUSE_DRAC"
+ fi])
# Check for libpthread. On FreeBSD, the libc_r does the job.
# On digitalUNIX, libpthreads (with a trailing s) is the library to use
@@ -645,13 +647,15 @@
# Check for DNSRBL
AC_ARG_ENABLE(dnsrbl,
[ --enable-dnsrbl Enable DNSRBL support],
- [if test $rdns = yes; then
- CFLAGS=$CFLAGS" -DUSE_DNSRBL"
- else
- echo "--enable-dnsrbl used but DNS resolver is not thread safe";
- echo "Try installing BIND9 and using --with-libbind, or if you";
- echo "know what you are doing, use --with-thread-safe-resolver";
- exit 1;
+ [if test x$enableval = xyes; then
+ if test $rdns = yes; then
+ CFLAGS=$CFLAGS" -DUSE_DNSRBL"
+ else
+ echo "--enable-dnsrbl used but DNS resolver is not thread safe";
+ echo "Try installing BIND9 and using --with-libbind, or if you";
+ echo "know what you are doing, use --with-thread-safe-resolver";
+ exit 1;
+ fi
fi
])
/FabienMessage
Re: [milter-greylist] configure and drac
2006-08-20 by Fabien Tassin
Attachments
- No local attachments were found for this message.