heya, this one fixes a rather cosmetic configure issue. configure didn't return exit 0 when there was no libol. diff -bur syslog-ng-1.5.2/configure syslog-ng-1.5.2.patched/configure --- syslog-ng-1.5.2/configure Mon Jan 15 11:08:31 2001 +++ syslog-ng-1.5.2.patched/configure Tue Jan 16 15:08:30 2001 @@ -2658,6 +2658,10 @@ echo "configure:2659: checking libol version >= $LIBOL_REQ_MAJOR.$LIBOL_REQ_MINOR.$LIBOL_REQ_PATCH" >&5 if test "$with_libol" = ""; then + if ! [ -x libol-config ]; then + echo "can't locate libol, aborting. Use --with-libol directive if it is installed" + exit 0 + fi LIBOL_VERSION=`libol-config --version` LIBOL_CFLAGS=`libol-config --cflags` LIBOL_LIBS=`libol-config --static-libs` diff -bur syslog-ng-1.5.2/configure.in syslog-ng-1.5.2.patched/configure.in --- syslog-ng-1.5.2/configure.in Mon Jan 15 11:08:20 2001 +++ syslog-ng-1.5.2.patched/configure.in Tue Jan 16 15:07:45 2001 @@ -137,6 +137,10 @@ AC_MSG_CHECKING(libol version >= $LIBOL_REQ_MAJOR.$LIBOL_REQ_MINOR.$LIBOL_REQ_PATCH) if test "$with_libol" = ""; then + if ! [ -x libol-config ]; then + echo "can't locate libol, aborting. Use --with-libol directive if it is installed" + exit 0 + fi LIBOL_VERSION=`libol-config --version` LIBOL_CFLAGS=`libol-config --cflags` LIBOL_LIBS=`libol-config --static-libs` -- Regards, Wiktor Wodecki Unix-Administration Wapme Systems AG