* m4/libtool.m4 (LT_CMD_MAX_LEN) [osf]: On Tru64 there could

be a kernel panic when testing the maximum command line length
if exec_disable_arg_limit=1. Don't do the tests to figure it
out on *-osf*.
Reported by Dr. Hans Ekkehard Plesser
<hans.ekkehard.plesser@umb.no>

diff --git a/ChangeLog b/ChangeLog
index b51cdf041382a750b8b67103d33e7b6f3b538565..2e4f546d104c3fa91f314d10f5f3466e19154c1e 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,12 @@
+2005-01-16  Peter O'Gorman  <peter@pogma.com>
+
+       * m4/libtool.m4 (LT_CMD_MAX_LEN) [osf]: On Tru64 there could
+       be a kernel panic when testing the maximum command line length
+       if exec_disable_arg_limit=1. Don't do the tests to figure it 
+       out on *-osf*.
+       Reported by Dr. Hans Ekkehard Plesser 
+       <hans.ekkehard.plesser@umb.no>
+
 2005-01-12  Guido Draheim  <guidod-2003-@gmx.de>  (tiny change)
 
        * m4/libtool.m4 (AC_PROG_SED): Don't break test loop early.

diff --git a/m4/libtool.m4 b/m4/libtool.m4
index 6834d53e84199703d55d3faa697276db8444da03..e49a0bd32d1eb3b40ab688f6b84f9f31d0212dae 100644 (file)
--- a/m4/libtool.m4
+++ b/m4/libtool.m4
@@ -1163,7 +1163,20 @@ AC_CACHE_VAL([lt_cv_sys_max_cmd_len], [dnl
     # And add a safety zone
     lt_cv_sys_max_cmd_len=`expr $lt_cv_sys_max_cmd_len \/ 4`
     ;;
- *)
+  osf*)
+    # Dr. Hans Ekkehard Plesser reports seeing a kernel panic running configure
+    # due to this test when exec_disable_arg_limit is 1 on Tru64. It is not
+    # nice to cause kernel panics so lets avoid the loop below.
+    # First set a reasonable default.
+    lt_cv_sys_max_cmd_len=16384
+    # 
+    if test -x /sbin/sysconfig; then
+      case `/sbin/sysconfig -q proc exec_disable_arg_limit` in
+        *1*) lt_cv_sys_max_cmd_len=-1 ;;
+      esac
+    fi
+    ;;
+  *)
     # Make teststring a little bigger before we do anything with it.
     # a 1K string should be a reasonable start.
     for i in 1 2 3 4 5 6 7 8 ; do