Ok, pambase/shadow problem solved. I called revdep-rebuild and it
found libcairo problem, reemerged it, second revdep-rebuild was clean.
There are still problems with compilation of packages mentioned above.

2014-04-27 22:10 GMT+03:00 Stroller <strol...@stellar.eclipse.co.uk>:
>
> On Sun, 27 April 2014, at 8:20 am, Nikita Tropin <posixivis...@gmail.com> 
> wrote:
>
>> gcc-config -l:
>> [1] x86_64-pc-linux-gnu-4.6.3
>> [2] x86_64-pc-linux-gnu-4.7.3 *
>>
>> These are installed: gcc-4.7.3, gcc-4.6.3, clang-3.3. I'm using 4.7.3
>> and not redefine CC or CXX in make.conf or elsewhere.
>
> That's good. gcc-4.7.3 is current, so you should be able to revdep-rebuild 
> and update glibc, paving your way to ncurses and your other failed compiles. 
> But IMO you should get the pam / shadow stuff done, and reboot, first.
>
>
>> I found that getting out `pam' flag from `shadow' flags removes block.
>> Is it suitable fix(add `-pam' for `shadow' in package.use)? Or ...
>>
>> As I can understand from
>> bugtracker(https://bugs.gentoo.org/show_bug.cgi?id=412721) I need to:
>> su # For doing administrative tasks while /etc/pam.d/{su,login,passwd} will 
>> gone
>> emerge shadow
>> emerge pambase
>> dispatch-conf && etc-update
>>
>> PS Thanks Edward, it helps.
>>
>>
>>> …  IMO you need to address the pambase/shadow block first.
>>>
>>> They're important packages and the transition is important.
>
> I intended to say here that "they're important packages and the transition is 
> well documented."
>
> I've already linked you pages and pages of information on this update:
> http://www.google.com/search?q=pambase+shadow+gentoo
>
> I *think* that you unmerge one or both packages and then reemerge, but I 
> can't remember for sure.
>
> It's also hard to say how safe this will be on a system that's in such 
> disrepair as yours - you might be best to backup the whole system &/or build 
> binary packages for everything that's presently installed. If you ignore 
> updates for a year at a time, you're really risking trouble.
>
> Stroller.
>
>
>



-- 
Regards,
Nikita

Reply via email to