All customers except US A&D: to ensure that you can access all of your product downloads, you must log in to the Wind River Delivers portal and visit the My Products page to force an initial sync of your product entitlement. Only after you’ve completed this step will you be able to access and download product content through the Artifacts, Registry, and Git interfaces. This also applies to users attempting to run the Wind River installer in maintenance or update mode or Linux installation updates at the command line.

Wind River Support Network

HomeOther DownloadsBug in pam package build in Wind River Linux 1.5
Recommended Type: Patch

Bug in pam package build in Wind River Linux 1.5

Released: Sep 19, 2008     Updated: Sep 19, 2008


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 in /host-cross/-wrs-linux-gnu/lib shows soft links i.e.
lrwxrwxrwx 1 user users 27 2008-09-11 13:29 -> ../../lib/
lrwxrwxrwx 1 user users 31 2008-09-11 13:29 -> ../../lib/
lrwxrwxrwx 1 user users 26 2008-09-11 13:29 -> ../../lib/
basically pointing to libs in /host-cross/libs and relevant libs are not present.

Ultimately shadow-utils builds without libpam.

Adding pam-devel to the pam Makefile does not make a difference. IDENTIFIER = WIND00134034

Product Version

Linux Platforms 1.x


Installation Notes

Installation Notes

  1. Unzip the patch under [install_dir]/updates

    2. Install the patch CD by entering the patch CD directory and run setup_linux.

    3. This is a source only patch so you will have to rebuild the pam package. Executing the command �make -C build pam.rebuild� can do this.

    4. Next issue a �make fs� to rebuild the root file system.

    5. Upload the kernel and root file system into the target and boot it up.

Live chat