On Tue, Aug 6, 2013 at 2:31 PM, Ken Moffat <[email protected]> wrote:

> On Tue, Aug 06, 2013 at 01:42:23PM -0500, Dave Wagler wrote:
> > I'm trying to install Polkit-0.111 with PAM support; the configure
> command
> > prints these messages (among many others):
> >
> > checking security/pam_modutil.h usability... yes
> > checking security/pam_modutil.h presence... yes
> > checking for security/pam_modutil.h... yes
> > checking security/pam_ext.h usability... yes
> > checking security/pam_ext.h presence... yes
> > checking for security/pam_ext.h... yes
> > checking for pam_vsyslog in -lpam... yes
> >         PAM support:                no
> >
> > I have installed Linux-PAM-1.1.6, and a Shadow-4.1.5.1 installation does
> > recognize PAM.
> >
> > Any thoughts on what might be wrong?
> >
> > Thanks,
> > Dave
>
>  PAM is one of those things in which I have no interest, but I guess
> the general method of working out how to build a package, or why a
> dependency is not apparently satisfied, is fairly common.
>
>  Try looking at the configure script.  Search for that pam_vsyslog
> message, then look at the next chunk of the file where it tests for
> 'PAM support:' so you can see how, and what, it tests.
>
>  Not every configure script is straightforward, but in many of them
> you can see a test for a string of pkgconfig files (unlikely here, I
> think) and in others you will see test programs trying to use a
> library function - like the pam_vsyslog test.
>
>  I will guess that you maybe got an error message (look in
> config.log), or else that PAM is perhaps turned off unless you
> specifically enable it.
>
> ĸen
>
> The polkit configure script is quite complicated. This is the only section
that looks significant:

have_pam=no
if test "$need_pam" = yes ; then
  { $as_echo "$as_me:${as_lineno-$LINENO}: checking for pam_start in -lpam"
>&5
$as_echo_n "checking for pam_start in -lpam... " >&6; }
if ${ac_cv_lib_pam_pam_start+:} false; then :
  $as_echo_n "(cached) " >&6
else
  ac_check_lib_save_LIBS=$LIBS
LIBS="-lpam  $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h.  */

/* Override any GCC internal prototype to avoid an error.
   Use char because int might match the return type of a GCC
   builtin and then its argument prototype would still apply.  */
#ifdef __cplusplus
extern "C"
#endif
char pam_start ();
int
main ()
{
return pam_start ();
  ;
  return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
  ac_cv_lib_pam_pam_start=yes
else
  ac_cv_lib_pam_pam_start=no
fi
rm -f core conftest.err conftest.$ac_objext \
    conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_pam_pam_start"
>&5
$as_echo "$ac_cv_lib_pam_pam_start" >&6; }
if test "x$ac_cv_lib_pam_pam_start" = xyes; then :
  have_pam=yes
fi

This is the only place in the script where have_pam can be set to yes. Can
you decipher what is being tested?

There do not appear to be any error messages in config.log.

This install is being run in a host system under chroot. How can PAM be
either turned off or enabled?

Dave
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to