Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 581306 - sys-auth/nss_ldap: wrong nss_ldap library name or missing simlink
Summary: sys-auth/nss_ldap: wrong nss_ldap library name or missing simlink
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: ARM Linux
: Normal major (vote)
Assignee: LDAP Herd
Depends on:
Reported: 2016-04-26 22:48 UTC by Hika
Modified: 2020-04-29 14:33 UTC (History)
2 users (show)

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

emerge --info (info,4.75 KB, text/plain)
2016-05-29 00:22 UTC, Hika
sys-auth:nss_ldap-265-r5:20160528-205134.log (SYS-AU~7.LOG,1.51 KB, text/plain)
2016-05-29 00:25 UTC, Hika

Note You need to log in before you can comment on or make changes to this bug.
Description Hika 2016-04-26 22:48:44 UTC
On the Raspberry Pi for the nss_ldap package the library /lib/ is created and it is not working.
On AMD64 the libraries are /lib64/ and /usr/lib32/
Creating a simlink on the Raspberry Pi to /lib/ enables logging in.
Next to that I have on the Raspberry Pi problems with an encrypted bindpw in /etc/ldap.conf. I have not jet pinpointed the cause. (missing kernel module/library?)

Reproducible: Always

Steps to Reproduce:
1.Install nss_ldap pam_ldap and openldap
2.enable linux login through ldap in pam.d, ldap.conf an nsswitch.conf
3.try to login
Comment 1 Hika 2016-04-29 01:48:12 UTC
Forget my mentioning of the problem with encrypted bindpw. While examining and testing, /etc/openldap/ldap.conf and /etc/ldap.conf got mixed up. The first accepts an encrypted bindpw, the second not.
Comment 2 SpanKY gentoo-dev 2016-05-05 06:12:33 UTC
please attach the full build log of nss_ldap and your emerge info.  all bugs reports should include these things.  it is hard for us to triage/debug w/out them.
Comment 3 Robert Holzknecht 2016-05-28 20:07:04 UTC
I can confirm this bug too.

Workaround by creating the symlink as explained: /lib/ -> /lib/

Raspberry Pi2 (ARMv7)
CFLAGS="-O2 -pipe -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard"
Comment 4 Robert Holzknecht 2016-05-28 20:08:04 UTC
Btw: I guess using qemu and compiling nss_ldap will bring the issue up...

If needed i'll rebuild nss_ldap again to provide the files.
Comment 5 Hika 2016-05-29 00:22:50 UTC
Created attachment 435666 [details]
emerge --info

Sorry I missed your request
Comment 6 Hika 2016-05-29 00:25:26 UTC
Created attachment 435668 [details]

And the emerge log
Comment 7 Hika 2016-05-29 00:26:14 UTC
I had to rerun it as my log had disappeared
Comment 8 Mikle Kolyada archtester Gentoo Infrastructure gentoo-dev Security 2018-04-22 09:44:00 UTC
nothing to do here for arm@
Comment 9 Stéphane Veyret 2020-04-29 14:33:03 UTC
Hi all,
I faced the same problem (4 years later) and found a correction which could be applied as a Gentoo patch.

Actually, the configure script does not detect that we are running with a glibc because its way for such detection is:

test "$target_os" = "linux" -o "$target_os" = "linux-gnu"

and target_os is the end of the CHOST, which for a Pi used to be "armv7a-hardfloat-linux-gnueabi" and is now "armv7a-unknown-linux-gnueabihf".

I managed to make it work adding

 -o "$target_os" = "linux-gnueabihf"

in both configure (line 4489) and (line 118) file, so a quick patch could easily be made.

Note that the downloaded source does not seem to be up to date with the visible sources under GitHub as the latter have an additional (but not working nowadays)

 -o "$target_os" = "linux-gnueabi"