| 1 |
On Sun, 27 April 2014, at 8:20 am, Nikita Tropin <posixivist32@×××××.com> wrote: |
| 2 |
|
| 3 |
> gcc-config -l: |
| 4 |
> [1] x86_64-pc-linux-gnu-4.6.3 |
| 5 |
> [2] x86_64-pc-linux-gnu-4.7.3 * |
| 6 |
> |
| 7 |
> These are installed: gcc-4.7.3, gcc-4.6.3, clang-3.3. I'm using 4.7.3 |
| 8 |
> and not redefine CC or CXX in make.conf or elsewhere. |
| 9 |
|
| 10 |
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. |
| 11 |
|
| 12 |
|
| 13 |
> I found that getting out `pam' flag from `shadow' flags removes block. |
| 14 |
> Is it suitable fix(add `-pam' for `shadow' in package.use)? Or ... |
| 15 |
> |
| 16 |
> As I can understand from |
| 17 |
> bugtracker(https://bugs.gentoo.org/show_bug.cgi?id=412721) I need to: |
| 18 |
> su # For doing administrative tasks while /etc/pam.d/{su,login,passwd} will gone |
| 19 |
> emerge shadow |
| 20 |
> emerge pambase |
| 21 |
> dispatch-conf && etc-update |
| 22 |
> |
| 23 |
> PS Thanks Edward, it helps. |
| 24 |
> |
| 25 |
> |
| 26 |
>> … IMO you need to address the pambase/shadow block first. |
| 27 |
>> |
| 28 |
>> They're important packages and the transition is important. |
| 29 |
|
| 30 |
I intended to say here that "they're important packages and the transition is well documented." |
| 31 |
|
| 32 |
I've already linked you pages and pages of information on this update: |
| 33 |
http://www.google.com/search?q=pambase+shadow+gentoo |
| 34 |
|
| 35 |
I *think* that you unmerge one or both packages and then reemerge, but I can't remember for sure. |
| 36 |
|
| 37 |
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. |
| 38 |
|
| 39 |
Stroller. |
Archives