Author: Lars Mueller <lmuelle@suse.com>
Subject: Make PAM security install directory configurable at compile time
Reported-upstream: yes
Bugzilla: bso#10513

Index: cifs-utils-6.3/configure.ac
===================================================================
--- cifs-utils-6.3.orig/configure.ac
+++ cifs-utils-6.3/configure.ac
@@ -58,6 +58,12 @@ AC_ARG_WITH(idmap-plugin,
 AC_DEFINE_UNQUOTED(IDMAP_PLUGIN_PATH, "$pluginpath", [Location of plugin that ID mapping infrastructure should use. (usually a symlink to real plugin)])
 AC_SUBST([pluginpath])
 
+AC_ARG_WITH(pamdir,
+	[AC_HELP_STRING([--with-pamdir=DIR],[Where to install the PAM module [[$(libdir)/security]]])],
+	pamdir=$withval,
+	pamdir="\$(libdir)/security")
+AC_SUBST([pamdir])
+
 # check for ROOTSBINDIR environment var
 if test -z $ROOTSBINDIR; then
 	ROOTSBINDIR="/sbin"
Index: cifs-utils-6.3/Makefile.am
===================================================================
--- cifs-utils-6.3.orig/Makefile.am
+++ cifs-utils-6.3/Makefile.am
@@ -92,8 +92,6 @@ idmapwb.8: idmapwb.8.in
 endif
 
 if CONFIG_PAM
-pamdir = $(libdir)/security
-
 pam_PROGRAMS = pam_cifscreds.so
 
 pam_cifscreds.so: pam_cifscreds.c cifskey.c resolve_host.c util.c