See below :) --- openpam-20050616-r1.ebuild 2007-02-06 16:05:19.000000000 +0100 +++ openpam-20050616-r1.ebuild 2007-09-10 21:28:52.000000000 +0200 @@ -5,7 +5,7 @@ WANT_AUTOCONF="latest" WANT_AUTOMAKE="latest" -inherit multilib flag-o-matic autotools +inherit multilib flag-o-matic autotools pam DESCRIPTION="Open source PAM library." HOMEPAGE="http://www.openpam.org/" @@ -42,7 +42,7 @@ src_compile() { econf \ --disable-dependency-tracking \ - --with-modules-dir=/$(get_libdir)/security \ + --with-modules-dir=/$(getpam_mod_dir) \ ${myconf} || die "econf failed" emake || die "emake failed"
Here's the logic from the eclass if has_version sys-libs/pam || has_version sys-libs/openpam; then PAM_MOD_DIR=/$(get_libdir)/security elif use ppc-macos; then # OSX looks there for pam modules PAM_MOD_DIR=/usr/lib/pam else # Unable to find PAM implementation... defaulting PAM_MOD_DIR=/$(get_libdir)/security fi echo ${PAM_MOD_DIR} As you can see, if linuxpam or openpam is NOT installed and the target is ppc-macos then it will install to /usr/lib/pam but subsequent calls will use /$(get_libdir)/security. Basically, that eclass function is for ebuilds that install pam modules but are not an actual pam implementation.
