Hi all, it seems the configure script acts differently for glibc-based and other systems. Therefore it tests the "target_os" variable for equality to the strings "linux" or "linux-gnu" (configure.inc line 101) to determine if it's a glibc based systems.
On armel systems the target_os variable contains "linux-gnueabi" therefore doesn't match and changes the build system to create the result reported. In the attached patch I simply added another possible string containing "linux-gnueabi" to this test. After an autoreconf it built and produced a package with the same file structure expected from the other architectures. Heiko
diff --git nss_ldap-264.orig/configure nss_ldap-264/configure index d61531c..52da797 100755 --- nss_ldap-264.orig/configure +++ nss_ldap-264/configure @@ -3422,7 +3422,7 @@ fi -if test "$target_os" = "linux" -o "$target_os" = "linux-gnu"; then +if test "$target_os" = "linux" -o "$target_os" = "linux-gnu" -o "$target_os" = "linux-gnueabi"; then GLIBC_TRUE= GLIBC_FALSE='#' else diff --git nss_ldap-264.orig/configure.in nss_ldap-264/configure.in index 0453cf1..964acf1 100644 --- nss_ldap-264.orig/configure.in +++ nss_ldap-264/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)
signature.asc
Description: This is a digitally signed message part.
