search for: pam_mod

...;) managed to get this thing to build. What he changed to get it to do so is the following: configure: Change all of the references to "<module>.so" to "<module>.$SHLIBEXT." This, to me, seems to be common sense. Anyone know why this wasn't done? (Particularly, PAM_MOD="bin/pam_smbpass.so") Makefile: Once this is generated, comment out the DYNEXP line: #DYNEXP=-Wl, -E ...this could obviously be done in configure too. This is correct syntax, so this seems to be more of an HP bug. Don't know WHY there is a problem with this syntax, be it an 11i bu...

...at +SPROGS = bin/smbd bin/nmbd @SWAT_PROG@ PROGS1 = bin/smbclient bin/smbspool bin/testparm bin/testprns bin/smbstatus bin/smbcontrol bin/tdbbackup bin/make_printerdef @RUNPROG@ PROGS2 = bin/smbpasswd bin/make_smbcodepage bin/rpcclient bin/make_unicodemap bin/smbcacls @WRAPPROG@ @WRAP@ @WRAP32@ @PAM_MOD@ @PDBEDIT@ @LIBSMBCLIENT@ MPROGS = @MPROGS@ @@ -103,7 +103,7 @@ TORTURE_PROGS = bin/smbtorture bin/msgtest bin/masktest bin/locktest bin/locktest2 SHLIBS = libsmbclient -SCRIPTS = $(srcdir)/script/smbtar $(srcdir)/script/findsmb +SCRIPTS = $(srcdir)/script/smbtar script/findsmb QUOTAOBJS=...