FreeBSD no longer needs the main sudo binary to link with -lpam

now that plug-ins are loaded with RTLD_GLOBAL.

diff --git a/configure b/configure
index 2c35a8da90ebe456166ffc143bdb21120c07bac4..6c2ab2c1cb69a9bc2e8b39638771421edc0c8872 100755 (executable)
--- a/configure
+++ b/configure
@@ -17133,14 +17133,6 @@ if test ${with_pam-"no"} != "no"; then
     # We already link with -ldl (see LIBDL below) so no need for that here.
     SUDOERS_LIBS="${SUDOERS_LIBS} -lpam"
 
-    # There should be no need to link the sudo front-end with PAM
-    # as all PAM calls happen via the sudoers plugin.
-    # Unfortunately, not doing so causes problems on FreeBSD at least.
-    case "$OS" in
-       freebsd)
-           LIBS="${LIBS} -lpam";;
-    esac
-
                     for ac_header in security/pam_appl.h pam/pam_appl.h
 do :
   as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`

diff --git a/configure.in b/configure.in
index da62eb65f61db04045f93fc38245e2524b97c90a..febe67c758e614800583354af344067bee8e3a1f 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -2306,14 +2306,6 @@ if test ${with_pam-"no"} != "no"; then
     # We already link with -ldl (see LIBDL below) so no need for that here.
     SUDOERS_LIBS="${SUDOERS_LIBS} -lpam"
 
-    # There should be no need to link the sudo front-end with PAM
-    # as all PAM calls happen via the sudoers plugin.
-    # Unfortunately, not doing so causes problems on FreeBSD at least.
-    case "$OS" in
-       freebsd)
-           LIBS="${LIBS} -lpam";;
-    esac
-
     dnl
     dnl Some PAM implementations (MacOS X for example) put the PAM headers
     dnl in /usr/include/pam instead of /usr/include/security...