From: Nikita Tropin <posixivist32@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OpenSP build fails
Date: Mon, 28 Apr 2014 20:47:59 +0300 [thread overview]
Message-ID: <CAL-+O4JgCYiKBpY2HB50R2CjLZgjrzNR1-B4=QVd+Pn7oQ_6Tw@mail.gmail.com> (raw)
In-Reply-To: <0DD1D7F5-B9FF-4BDF-98E3-89F0CE32D271@stellar.eclipse.co.uk>
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 <stroller@stellar.eclipse.co.uk>:
>
> On Sun, 27 April 2014, at 8:20 am, Nikita Tropin <posixivist32@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
next prev parent reply other threads:[~2014-04-28 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL-+O4LXftSDG4=jpXgybak3JO65q8cR_CU2KF2m8+BmWFmBAg@mail.gmail.com>
2014-04-22 15:40 ` [gentoo-user] Fwd: OpenSP build fails Nikita Tropin
2014-04-22 15:40 ` [gentoo-user] " Nikita Tropin
2014-04-22 16:23 ` [gentoo-user] Fwd: " Edward M
2014-04-22 19:05 ` Nikita Tropin
2014-04-22 19:53 ` Edward M
2014-04-23 16:36 ` [gentoo-user] " Stroller
2014-04-23 16:49 ` Stroller
2014-04-23 18:20 ` Nikita Tropin
2014-04-23 23:33 ` Stroller
2014-04-23 23:54 ` Stroller
2014-04-26 21:07 ` Nikita Tropin
2014-04-26 21:23 ` Edward M
2014-04-27 1:44 ` Stroller
2014-04-27 7:20 ` Nikita Tropin
2014-04-27 19:10 ` Stroller
2014-04-28 17:47 ` Nikita Tropin [this message]
2014-04-22 15:42 Nikita Tropin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL-+O4JgCYiKBpY2HB50R2CjLZgjrzNR1-B4=QVd+Pn7oQ_6Tw@mail.gmail.com' \
--to=posixivist32@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox