Re: linuxconf fails to dlopen pam under glibc 2.0.99

[hjl@lucon.org (H.J. Lu)]

> 
> Ulrich,
>    I believe I have found a cross-platform flaw in glibc 2.0.99. On
> linuxppc running linux 2.1.125 with glibc 2.0.99 compiled with
> egcs_1_1_branch cvs of this week I am finding the following problem
> with linuxconf 1.3r1. While linuxconf runs correctly in general if
> one attempts to change the password of a user from it the following
> error messages appear in /var/log/messages each time...
> 
> Oct 29 19:14:17 dilbert pam[556]: unable to dlopen(/lib/security/pam_pwdb.so)
> Oct 29 19:14:17 dilbert pam[556]: [dlerror: /lib/security/pam_pwdb.so: undefined
>  symbol: pam_get_item]
> Oct 29 19:14:17 dilbert pam[556]: adding faulty module: /lib/security/pam_pwdb.s
> o
> Oct 29 19:14:17 dilbert pam[556]: unable to dlopen(/lib/security/pam_cracklib.so
> )
> Oct 29 19:14:17 dilbert pam[556]: [dlerror: /lib/security/pam_cracklib.so: undef
> ined symbol: pam_get_item]
> Oct 29 19:14:17 dilbert pam[556]: adding faulty module: /lib/security/pam_crackl
> ib.so 
> 
> Tom Rini has verified the same behavior on Intel linux under glibc 2.0.99.
> Could you look into this one?
>                      Jack
> 

I have no problem with linuxconf-1.11r11-rh3 and the current glibc
in CVS. pam_get_item is defined in /lib/libpam.so.


-- 
H.J. Lu (hjl@gnu.org)