From 69fe59a6324095d47629b9dc22bc5d550178a0c3 Mon Sep 17 00:00:00 2001 From: nekral-guest Date: Sun, 3 May 2009 22:46:26 +0000 Subject: [PATCH] * NEWS, configure.in: Fix build failure on non-PAM enabled system when --without-pam is not specified. --- ChangeLog | 5 +++++ NEWS | 4 +++- configure.in | 1 + 3 files changed, 9 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index 5fe6cbf0..3634ca57 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2009-05-04 Nicolas François + + * NEWS, configure.in: Fix build failure on non-PAM enabled system + when --without-pam is not specified. + 2009-04-30 Nicolas François * lib/commonio.c: Ignore teh return values of fclose() and diff --git a/NEWS b/NEWS index 092ac85e..7da682ad 100644 --- a/NEWS +++ b/NEWS @@ -4,8 +4,10 @@ shadow-4.1.3.1 -> shadow-4.1.3.2 UNRELEASED - packaging * Enable --enable-account-tools-setuid by default for PAM builds. - * Added configure option --enable-utmpx, disabled by default to mimic + * Add configure option --enable-utmpx, disabled by default to mimic the previous behavior on Linux (where utmp and utmpx are identical). + * Fix build failure on non-PAM systems when --without-pam is not + specified. - login * Do not trust the current utmp entry's ut_line to set PAM_TTY. This could lead to DOS attacks. diff --git a/configure.in b/configure.in index dca1cf0d..b9f0ca05 100644 --- a/configure.in +++ b/configure.in @@ -417,6 +417,7 @@ if test "$with_libpam" != "no"; then with_libpam="yes" else with_libpam="no" + unset LIBPAM fi fi dnl Now with_libpam is either yes or no