View previous topic :: View next topic |
Author |
Message |
hika Apprentice
Joined: 13 Mar 2009 Posts: 234 Location: Utrecht
|
Posted: Fri Dec 13, 2013 10:34 pm Post subject: Latest amd64 stages broken for nss_ldap [solved] |
|
|
Last week I had problems with emerging sys-auth/nss-ldap on a fresh system. I got the following emerge error.
Code: | [33;01m*[0m QA Notice: Package triggers severe warnings which indicate that it
[33;01m*[0m may exhibit random runtime failures.
[33;01m*[0m ldap-nss.c:586:3: warning: implicit declaration of function '__libc_lock_lock' [-Wimplicit-function-declaration]
[33;01m*[0m ldap-nss.c:632:3: warning: implicit declaration of function '__libc_lock_unlock' [-Wimplicit-function-declaration]
[33;01m*[0m ldap-nss.c:1254:3: warning: implicit declaration of function '__libc_once' [-Wimplicit-function-declaration]
[33;01m*[0m util.c:97:3: warning: implicit declaration of function '__libc_lock_lock' [-Wimplicit-function-declaration]
[33;01m*[0m util.c:104:4: warning: implicit declaration of function '__libc_lock_unlock' [-Wimplicit-function-declaration]
[33;01m*[0m Please do not file a Gentoo bug and instead report the above QA
[33;01m*[0m issues directly to the upstream developers of this software.
[33;01m*[0m Homepage: http://www.padl.com/OSS/nss_ldap.html
[32;01m*[0m If you use a ldaps:// string in the 'uri' setting of
[32;01m*[0m your /etc/ldap.conf, you must set 'ssl on'! |
After enabling ldap trying to login gives
Code: | traps: login[1787] general protection ip:7f40e100f828 sp:6cc0cd81b980c468 error:0 in ld-2.16.so[7f40e0ff8000+22000] |
where the number after ip: differs.
su gives:
Code: | su: symbol lookup error: /lib64/libnss_ldap.so.2: undefined symbol: __libc_lock_lock |
Although it says it has to do with upstream, I have never seen it before and retrying with Quote: | stage3-amd64-20131010.tar.bz2 | the problem doesn't show. Both Quote: | stage3-amd64-20131205.tar.bz2 | and Quote: | stage3-amd64-20131010.tar.bz2 | show the problem.
I've been trying to further locate the cause. I've tried remerging both gcc and glibc and stepping back a gcc version. Without result.
Can anybody show some light and maybe fix it with the newer stage3 files.
Hika
Last edited by hika on Sun Dec 15, 2013 4:46 pm; edited 1 time in total |
|
Back to top |
|
|
hika Apprentice
Joined: 13 Mar 2009 Posts: 234 Location: Utrecht
|
Posted: Sat Dec 14, 2013 2:18 am Post subject: |
|
|
These are the package differences between 20131205 an 20131010. Of cause it can also be in some differences in the base settings.
Code: | stage3-amd64-20131205 stage3-amd64-20131010
app-arch/unzip-6.0-r3 --
app-arch/xz-utils-5.0.5-r1 5.0.4-r1
app-misc/pax-utils-0.7 0.4
app-text/docbook-xml-dtd-4.1.2-r6 --
app-text/sgml-common-0.6.3-r5 --
dev-lang/python-3.3.2-r2 3.2.5-r2
dev-libs/expat-2.1.0-r3 2.1.0-r2
dev-libs/gmp-5.1.2 5.0.2_p1
dev-libs/mpfr-3.1.2-r1 3.1.1
dev-util/gperf-3.0.4 --
net-misc/netifrc-0.1 --
sys-apps/hwids-20130915.1 --
sys-apps/kmod-15 13-r1
sys-apps/man-pages-3.53 3.51
sys-apps/openrc-0.12.4 0.11.8
sys-apps/portage-2.2.7 2.2.1
sys-auth/pambase-20120417-r3 20120417-r2
sys-fs/udev-208 204
sys-libs/glibc-2.16.0 2.15-r3
sys-libs/zlib-1.2.8-r1 1.2.7
virtual/udev-208 200 |
The most likely candidates are glibc, pambase, maybe openrc or portage. Although I had portage updated before merging nss_ldap.
Is nss_ldap (partially) in python?
Once I have my system stable I'll look further.
Hika |
|
Back to top |
|
|
hika Apprentice
Joined: 13 Mar 2009 Posts: 234 Location: Utrecht
|
Posted: Sat Dec 14, 2013 6:10 pm Post subject: |
|
|
It's glibc-2.16.0. Once I update it from 2.15-r3 nss_ldap keeps working, but remerging breaks it with the above error.
I see about existing bugs or file one.
Hika |
|
Back to top |
|
|
hika Apprentice
Joined: 13 Mar 2009 Posts: 234 Location: Utrecht
|
Posted: Sat Dec 14, 2013 10:46 pm Post subject: |
|
|
I filled a bug, but if you encounter this problem and you have a similar system with working nss_ldap, you can try copying from the working system /lib64/libnss_ldap-2.15.so to /lib64/libnss_ldap-2.16.so on the broken system. Check where the simlink /lib64/libnss_ldap.so.2 is pointing to. It worked with me. It might be worth to save a copy of this file as fall back.
Hika |
|
Back to top |
|
|
hika Apprentice
Joined: 13 Mar 2009 Posts: 234 Location: Utrecht
|
Posted: Sun Dec 15, 2013 4:45 pm Post subject: |
|
|
nss_ldap-265-r2 seems to solve the problem. It is still masked instable so you have to add
Code: | =sys-auth/nss_ldap-265-r2 ~amd64 | to package.keywords. (or ~x86 if you use that.)
Hika |
|
Back to top |
|
|
|