Reopening this bug because updated ebuild file that doesn't use PREFIX hasn't fix the problem in my environment. Adding "/" to the beginning of sbin/unix_chkpwd in ebuild file fixed the error. Reproducible: Always Steps to Reproduce: 1.emerge-lakitu pam 2. 3.
Created attachment 687474 [details] emerge--info
Created attachment 687477 [details] emerge-lakitu--info
Created attachment 687480 [details] logs
Please let me know if there is any other data I can provide on my side.
Looks like a duplicate of bug 771132
The confusion comes from how this only matters in two cases: 1) Gentoo Prefix (where PAM doesn't make sense) 2) --root and so on Using "${ROOT}"/sbin/unix_chkpwd should work fine instead. Can you confirm?
*** Bug 771132 has been marked as a duplicate of this bug. ***
Hm. The eclass is supposed to prefix it with ${ROOT} for us. "If the file is a relative path (e.g. bin/foo rather than /bin/foo), then the appropriate path var ($D/$ROOT/etc...) will be prefixed based on the current ebuild phase." (https://devmanual.gentoo.org/eclass-reference/fcaps.eclass/index.html) Why isn't it?
Based on emerge --info and the build log, this appears to be a bug report for ChromiumOS, not Gentoo. Does the ChromiumOS repository include this eclass change? https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=06ac51cf5bdb3220d427819cdfafdab231e4a4f8
Looks like eclass change doesn't exist. I just verified that it fixes the error. Thank you for your time Mike and Sam!
