On 11/09/2013 00:22, Timur Aydin wrote:
> On 09/11/13 00:01, Alan McKinnon wrote:
>> I suspect your make.conf is faulty.
>>
>> What is the contents of make.conf?
>> what is ls -al $PORTDIR/eclass/pam.eclass
>>
>
> Here are the contents of /etc/portage/make.conf:
>
> ======================================================================
> # These settings were set by the catalyst build script that automatically
> # built this stage.
> # Please consult /usr/share/portage/config/make.conf.example for a more
> # detailed example.
> CFLAGS="-O2 -pipe"
> CXXFLAGS="${CFLAGS}"
> # WARNING: Changing your CHOST is not something that should be done lightly.
> # Please consult http://www.gentoo.org/doc/en/change-chost.xml before
> changing.
> CHOST="x86_64-pc-linux-gnu"
> # These are the USE flags that were used in addition to what is provided
> by the
> # profile used for building.
> MAKEOPTS="-j8"
> GENTOO_MIRRORS="ftp://ftp.linux.org.tr/pub/gentoo";
> USE="nptl nptlonly unicode minizip tk udev python threads xvfb perl dlz
> caps sqlite upcall systemd -gtk2 -gtk3 -acl"
> ACCEPT_KEYWORDS="~amd64"
> ACCEPT_LICENSE="*"
> VIDEO_CARDS="intel"
> INPUT_DEVICES="evdev keyboard mouse"
> FEATURES="-test"
> PORTDIR_OVERLAY="/usr/local/portage"
> ======================================================================
>
> And here is the pam.eclass perms:
>
> bonsai ~ # ls -al /usr/portage/eclass/pam.eclass
> -rw-r--r-- 1 portage portage 6455 Aug 5 2012
> /usr/portage/eclass/pam.eclass
I can't reproduce that fault here, and google hits on the matter seem to
point towards stale metadata referencing eclasses that no longer exist.
I have a hunch you do not have valid metadata for your local overlay, so
I suggest:
1. delete the eclass directory from your overlay, run "emerge
--metadata" and emerge samba again. See what that does.
2. Set PORTDIR_CACHE_METHOD and/or OVERLAY_CACHE_METHOD explicitly in
make.conf, the best reference for these is in the eix man page
--
Alan McKinnon
alan.mckin...@gmail.com
