sys-libs/pam-0.99.9.0 cannot be cross compiled under certain conditions. The problem are the following lines in the ebuild: - if sed -e 's:#.*::' /etc/pam.d/* | fgrep -q pam_stack.so; then - if sed -e 's:#.*::' /etc/pam.d/* | egrep -q 'pam_(pwdb|radius|timestamp|console)'; then - if sed -e 's:#.*::' /etc/pam.d/* | fgrep -q ${module}.so; then Because of the absolute path to /etc/pam.d the ebuild will check the files from the host and not the files from the target. If something is not properly set up on the host, cross emerge will fail wrongly. An interesting but for me unimportant question is: how could I get pam-0.99.9.0 on my host? My workaround is to replace /etc with ${SYSROOT}/etc in the ebuild. (SYSROOT points to the target filesystem and must be set) There is an other little problem in this ebuild: The dependency on flex isn't listed. But pam needs libfl provided by the flex package. Because flex is part of the system profile, this unpleasant problem normaly never happens. Reproducible: Always Steps to Reproduce: 1. Setup an old /etc/pam.d 2. setup corss environment 3. cross compile pam
has nothing to do with devrel SYSROOT is not a valid variable ... it should be checking ROOT ... not a cross-compiling issue, just related
Thanks for reporting, I've fixed the two issues in 0.99.9.0.
(In reply to comment #2) > Thanks for reporting, I've fixed the two issues in 0.99.9.0. > Yes, should be ROOT, not SYSROOT. Thanks a lot for this fix.
