494266 – sys-auth/nss_ldap-265-r1 with sys-libs/glibc-2.16.0 - QA Notice: ldap-nss.c:586:3: warning: implicit declaration of function '__libc_lock_lock' [-Wimplicit-function-declaration]

Bug 494266 - sys-auth/nss_ldap-265-r1 with sys-libs/glibc-2.16.0 - QA Notice: ldap-nss.c:586:3: warning: implicit declaration of function '__libc_lock_lock' [-Wimplicit-function-declaration]

Summary: sys-auth/nss_ldap-265-r1 with sys-libs/glibc-2.16.0 - QA Notice: ldap-nss.c:5...

Status:	RESOLVED UPSTREAM

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	AMD64 Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:	http://www.padl.com/OSS/nss_ldap.html
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2013-12-14 19:16 UTC by Hika
Modified:	2013-12-16 19:01 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
An unbroken emerge log (SYS-AU~0.LOG,20.98 KB, text/plain) 2013-12-14 19:17 UTC, Hika	Details
a broken emerge log (SYS-AU~V.LOG,22.81 KB, text/plain) 2013-12-14 19:18 UTC, Hika	Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Hika 2013-12-14 19:16:02 UTC

As long as glibc-2.15-r3 is installed nss_ldap-265-r1 merges and functions OK. Upgrading to glibc-2.16.0 doesn't immediately break it but remerging nss_ldap-265-r1 afterwards does. Emerging nss_ldap-265-r1 on newer stage3 (after october 10th ?) always results in a broken nss_ldap. I tried both 20131205 and 20131212.
Trying to login gives: "traps: login[1787] general protection ip:7f40e100f828 sp:6cc0cd81b980c468 error:0 in ld-2.16.so[7f40e0ff8000+22000]" with the sp: number differing. su gives: "su: symbol lookup error: /lib64/libnss_ldap.so.2: undefined symbol: __libc_lock_lock".



Reproducible: Always

Comment 1 Hika 2013-12-14 19:17:39 UTC

Created attachment 365334 [details]
An unbroken emerge log

Comment 2 Hika 2013-12-14 19:18:24 UTC

Created attachment 365336 [details]
a broken emerge log

Comment 3 Hika 2013-12-14 19:20:32 UTC

See also Forum thread http://forums.gentoo.org/viewtopic-t-978486.html

Comment 4 Hika 2013-12-14 21:12:11 UTC

copying libnss_ldap-2.15.so (85128 bytes) from a working installation to libnss_ldap-2.16.so (85160 bytes) on a broken system seems to fix the problem

Comment 5 Milan Beneš 2013-12-15 15:46:03 UTC

I confirm this bug. I waited with a major upgrade until KDE 4.11.2 got stabilised, did "emerge -e world" twice and ended up with a broken system, exactly in the manner described here.

Comment 6 Milan Beneš 2013-12-15 16:06:56 UTC

It seems that nss_ldap-265-r2 solves the issue.

Comment 7 Hika 2013-12-15 16:12:05 UTC

If so please confirm. My systems are now working, so I don't like to try.
Could then maintenance on merging may be add a glibc check, so you get the right one?

Comment 8 Hika 2013-12-15 16:40:51 UTC

Ok that seems to work. I'll add it to the forum thread

Comment 9 Jeroen Roovers (RETIRED) gentoo-dev

2013-12-16 19:01:25 UTC

 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: http://www.padl.com/OSS/nss_ldap.html