| 1 |
Am 27.11.2011 01:59, schrieb Paul Hartman: |
| 2 |
> On Sat, Nov 26, 2011 at 6:25 PM, Adam Carter <adamcarter3@×××××.com> wrote: |
| 3 |
>>>>>>> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by |
| 4 |
>>>>>>> /lib64/libcrypt.so.1) |
| 5 |
>>>>>>> |
| 6 |
>>>>>>> There were no @preserved-rebuild and revdep-rebuild found nothing. I |
| 7 |
>>>>>>> rebuilt pam and things seem to be working again. Are there any other |
| 8 |
>>>>>>> packages I should rebuild before encountering a problem? Or some way |
| 9 |
>>>>>>> to detect which need to be rebuilt? Should I re-emerge world against |
| 10 |
>>>>>>> my new glibc? :) |
| 11 |
>> |
| 12 |
>> How did you know to rebuild pam? |
| 13 |
>> |
| 14 |
>> Both /lib64/libc.so.6 and /lib64/libcrypt.so.1 are from glibc, and I |
| 15 |
>> interpret your error as 'libcrypt.so.1 couldn't find a GLIBC_2.14 |
| 16 |
>> version of /lib64/libc.so.6', which doesn't make any sense to me as |
| 17 |
>> both files are from the same package. How could the version dependency |
| 18 |
>> between them be incorrect? |
| 19 |
> |
| 20 |
> Sorry, I accidentally pasted the incomplete error message. It was part |
| 21 |
> of this kind of message in my syslog: |
| 22 |
> |
| 23 |
> Nov 25 19:40:01 [cron] PAM unable to |
| 24 |
> dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version |
| 25 |
> `GLIBC_2.14' not found (required by /lib64/security/pam_unix.so) |
| 26 |
> Nov 25 19:40:01 [cron] PAM adding faulty module: /lib64/security/pam_unix.so |
| 27 |
> |
| 28 |
|
| 29 |
THAT is the reason why neither revdep-rebuild nor @preserved-rebuild |
| 30 |
found pam. It dynamically loads libraries using dlopen instead of |
| 31 |
letting the dynamic linker handle it when the application is started. |
| 32 |
There is no reasonable way for revdep-rebuild to find these issues. |
| 33 |
|
| 34 |
Regards, |
| 35 |
Florian Philipp |
Archives