[svn] Provide a default for AC_TRY_RUN in SSL detection so that cross-compiling

has a chance of working.
Published in <sxspucwwkry.fsf@florida.arsdigita.de>.

diff --git a/ChangeLog b/ChangeLog
index ae49e762df1f3febfa09934e46943114f8d1da09..7fa80d1f210ccc228d3a6129fb25ec501356ec7b 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2001-05-26  Hrvoje Niksic  <hniksic@arsdigita.com>
+
+       * configure.in: Provide a default for AC_TRY_RUN when
+       cross-compiling.  Effectively, assume that when cross-compiling,
+       working linkage implies working executable.
+
 2001-05-25  Hrvoje Niksic  <hniksic@arsdigita.com>
 
        * configure.in: Rewrote OpenSSL library detection.  Now the code

diff --git a/configure.in b/configure.in
index 6e5be5e921ecb689be2969ebd9bdabb42fe2d756..27c0d535603fddf07510e0f0ab5353d3ccb793f9 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -287,7 +287,15 @@ if test x"$with_ssl" != x -a x"$with_ssl" != x"no"; then
     AC_CHECK_LIB(crypto,RSA_new,,ssl_link_failure=yes)
     AC_CHECK_LIB(ssl,SSL_new,,ssl_link_failure=yes)
 
-    dnl echo $LDFLAGS
+    dnl If ssl_link_failure is still no, the libraries link.  But we
+    dnl still need to check if the program linked with those libraries
+    dnl under these settings with run.  On some systems (Solaris), Gcc
+    dnl adds -L/usr/local/lib to the linking line, but fails to add
+    dnl -R/usr/local/lib, thus creating executables that link, but
+    dnl fail to run.
+
+    dnl If we are cross-compiling, just assume that working linkage
+    dnl implies working executable.
 
     if test x"$ssl_link_failure" = xno; then
       dnl Now try to run the thing.
@@ -296,7 +304,7 @@ if test x"$with_ssl" != x -a x"$with_ssl" != x"no"; then
 char RSA_new();
 char SSL_new();
 main(){return 0;}
-], AC_MSG_RESULT("yes"), AC_MSG_RESULT("no"); ssl_link_failure=yes)
+], AC_MSG_RESULT("yes"), AC_MSG_RESULT("no"); ssl_link_failure=yes, true)
     fi
 
     if test x"$ssl_link_failure" = xno; then