[EMAIL PROTECTED] wrote:
>
> Alexander Bokovoy writes:
>
> > It means that PAM (Pluggable Authentication Modules) support was enabled but your
> > system lacks PAM. Again.
>
> Ok I had midgard up and running on the machine before I tried to upgrade to
> 1.4b5. Is PAM something that it needs that it didn't before? What is the
> easiest workable hack for this problem? I'm not to sure where I can find
> PAM and I'm not in a position to do a reinstall of slackware at this point.
Midgard has no dependencies on PAM at all. PHP has only one mention of PAM in
configure.in where it tests for PAM presence in system and silently tries to link
with it to be sure that things will work as supposed. What you can do is to comment
out PAM test in configure.in if your system lacks PAM modules:
replace
dnl If libpam is available, we might need it
AC_CHECK_LIB(pam, pam_start, [
LIBS="-lpam $LIBS"
AC_DEFINE(HAVE_LIBPAM) ],
[])
with
dnl If libpam is available, we might need it
dnl AC_CHECK_LIB(pam, pam_start, [
dnl LIBS="-lpam $LIBS"
dnl AC_DEFINE(HAVE_LIBPAM) ],
[])
Be sure to run autoconf after this change. Config.h by default disables PAM so it
might help.
Another solution is to find libpam.a or libpam.so on your system and check it.
--
Sincerely yours, Alexander Bokovoy
The Midgard Project | www.midgard-project.org | Aurora R&D team
Minsk Linux Users Group | www.minsk-lug.net | www.aurora-linux.com
IPLabs Linux Team | linux.iplabs.ru | Architecte Open Source
-- To err is humor.
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
