There is a problem with the pam package and how other packages with dependencies on pam interact. Shadow-utils is one example of this problem.
When shadow-utils builds it is built with option --with-libpam so pam libraries should be linked, if available. However since pam libraries are not available, due to a problem in install rules, they are just ignored.
This problem does not appear in Wind River Linux 2.0.
When configuring the shadow-utils difference can be seen in the log files:
checking for pam_start in -lpam… no (Wind River Linux 1.5)
checking for pam_start in -lpam… yes (Wind River Linux 2.0)
ls -l pam.so in
lrwxrwxrwx 1 user users 27 2008-09-11 13:29 libpamc.so -> ../../lib/libpamc.so.0.81.0
lrwxrwxrwx 1 user users 31 2008-09-11 13:29 libpam_misc.so -> ../../lib/libpam_misc.so.0.81.2
lrwxrwxrwx 1 user users 26 2008-09-11 13:29 libpam.so -> ../../lib/libpam.so.0.81.3
basically pointing to libs in
Ultimately shadow-utils builds without libpam.
Adding pam-devel to the pam Makefile does not make a difference. IDENTIFIER = WIND00134034