From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.14.1 upgrade
Date: Sun, 27 Nov 2011 11:25:09 +1100 [thread overview]
Message-ID: <CAC=wYCFgYBTWHmadszm=bqaePkpy-Z2-TTfJnHZ8axeG89Ax_w@mail.gmail.com> (raw)
In-Reply-To: <CAEH5T2NUci_ssSjiGcojY8E-3D2qYp06zkdfTRw=TjaBfod38Q@mail.gmail.com>
>>> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
>>> >> /lib64/libcrypt.so.1)
>>> >>
>>> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
>>> >> rebuilt pam and things seem to be working again. Are there any other
>>> >> packages I should rebuild before encountering a problem? Or some way
>>> >> to detect which need to be rebuilt? Should I re-emerge world against
>>> >> my new glibc? :)
How did you know to rebuild pam?
Both /lib64/libc.so.6 and /lib64/libcrypt.so.1 are from glibc, and I
interpret your error as 'libcrypt.so.1 couldn't find a GLIBC_2.14
version of /lib64/libc.so.6', which doesn't make any sense to me as
both files are from the same package. How could the version dependency
between them be incorrect?
next prev parent reply other threads:[~2011-11-27 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 5:27 [gentoo-user] glibc-2.14.1 upgrade Paul Hartman
2011-11-24 7:34 ` justin
2011-11-25 16:30 ` 微菜
2011-11-25 18:11 ` Pandu Poluan
2011-11-25 18:59 ` Florian Philipp
2011-11-25 22:30 ` Neil Bothwick
2011-11-25 22:39 ` Albert W. Hopkins
2011-11-25 22:53 ` Michael Mol
2011-11-25 23:44 ` Volker Armin Hemmann
2011-11-26 16:06 ` Paul Hartman
2011-11-27 0:25 ` Adam Carter [this message]
2011-11-27 0:59 ` Paul Hartman
2011-11-27 10:53 ` Florian Philipp
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='CAC=wYCFgYBTWHmadszm=bqaePkpy-Z2-TTfJnHZ8axeG89Ax_w@mail.gmail.com' \
--to=adamcarter3@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