tag #511750 + confirmed patch severity #511750 serious forwarded #511750 http://bugzilla.padl.com/show_bug.cgi?id=402 stop
Hi I confirm this in 264-2; package build log on armel shows these files: -rw-r--r-- root/root 72704 2009-03-01 10:48 ./lib/nss_ldap.so.1 lrwxrwxrwx root/root 0 2009-03-01 10:47 ./usr/lib/libnss_ldap.so -> /lib/libnss_ldap.so.2 lrwxrwxrwx root/root 0 2009-03-01 10:47 ./lib/nss_ldap.so -> nss_ldap.so.1 While i386 correctly has: -rw-r--r-- root/root 76868 2009-03-01 08:50 ./lib/libnss_ldap-2.9.so lrwxrwxrwx root/root 0 2009-03-01 08:50 ./lib/libnss_ldap.so.2 -> libnss_ldap-2.9.so lrwxrwxrwx root/root 0 2009-03-01 08:50 ./usr/lib/libnss_ldap.so -> /lib/libnss_ldap.so.2 The file list on amd64 also seems correct (similar to i386): /lib/libnss_ldap-2.9.so /lib/libnss_ldap.so.2 /usr/lib/libnss_ldap.so There are some small variants, e.g. mipsel has: -rw-r--r-- root/root 94236 2009-03-01 09:38 ./lib/libnss_ldap-2.7.so lrwxrwxrwx root/root 0 2009-03-01 09:38 ./usr/lib/libnss_ldap.so -> /lib/libnss_ldap.so.2 lrwxrwxrwx root/root 0 2009-03-01 09:38 ./lib/libnss_ldap.so.2 -> libnss_ldap-2.7.so but that seems ok still. The difference in installation steps in the build log indicates that GLIBC isn't set on armel. It seems this is due to this test in configure.in: AM_CONDITIONAL(GLIBC, test "$target_os" = "linux" -o "$target_os" = "linux-gnu") See also https://bugs.launchpad.net/nss-ldap/+bug/387576 (Note that the latest upstream release is also affected.) Bye -- Loïc Minier
diff --git a/configure.in b/configure.in index 0453cf1..964acf1 100644 --- a/configure.in +++ b/configure.in @@ -98,7 +98,7 @@ linux*) nss_ldap_so_LDFLAGS="-shared -Wl,-Bdynamic -Wl,--version-script,\$(srcdi esac AM_CONDITIONAL(GCC, test "$GCC" = "yes") -AM_CONDITIONAL(GLIBC, test "$target_os" = "linux" -o "$target_os" = "linux-gnu") +AM_CONDITIONAL(GLIBC, test "$target_os" = "linux" -o "$target_os" = "linux-gnu" -o "$target_os" = "linux-gnueabi") AM_CONDITIONAL(AIX, test "$TARGET_OS" = AIX) AM_CONDITIONAL(HPUX, test "$TARGET_OS" = HPUX)