![]() |
-----Original Message----- From: Lee Howard > Did you re-run configure after installing pam-devel? I did, but configure was just re-using its cache file, so I ran 'make clean' and rm'ed config.cache. Still didn't work. So now, I just ran make distclean (after discovering it), and let that nuke things a bit, and now the compile works, both with and without the config.h ref in Login.c++, and hfaxd is indeed linked against libpam. My mistake here was not purging the build directory prior to a rebuild, a habit I have from other projects that let you get away with minor changes like adding in missing headers. There must've been another file aside from config.cache that was storing some temp data that was breaking things that only distclean purged. Hmm, funny enough, I just discovered the ldap patch, which might be more appplicable, so that I can control logins based on group memberships in my eDirectory backend... I'll have to toy with that tomorrow. Write this one off as PEBKAC :) Cheers!, --Josh ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*