libtool.m4: Update hardcode_shlibpath_var for OpenBSD

When generating an executable in OpenBSD, the executable fails to
generate when shlibpath_var, LD_LIBRARY_PATH, is used solely to
locate dependent libraries.

For hardcoding library paths in OpenBSD, see documentation for
hardcode_direct and hardcode_libdir_flag_spec.

* m4/libtool.m4: Update hardcode_shlibpath_var from 'no' to 'unsupported'
  by removing 'with_gnu_ld=no' for OpenBSD.

diff --git a/m4/libtool.m4 b/m4/libtool.m4
index d0d36865919efff195a1ee5eb8f2e9b3eb8337f7..2955adebf26978a4002ec55c55e009a4cb9a70e3 100644 (file)
--- a/m4/libtool.m4
+++ b/m4/libtool.m4
@@ -5091,9 +5091,6 @@ dnl Note also adjust exclude_expsyms for C++ above.
     # we just hope/assume this is gcc and not c89 (= MSVC++ or ICC)
     with_gnu_ld=yes
     ;;
-  openbsd*)
-    with_gnu_ld=no
-    ;;
   esac
 
   _LT_TAGVAR(ld_shlibs, $1)=yes