FYI: SCO/bugfix patch 1 of 10: AC_LIBTOOL_SYS_MAX_CMD_LEN

[Ralf Wildenhues]

Hi Kean, Tim,

* Kean Johnston wrote on Mon, Oct 31, 2005 at 04:28:11PM CET:
> Yes your simplified sed looks fine. Thanks!

* Tim Rice wrote on Mon, Oct 31, 2005 at 07:14:27PM CET:
> On Mon, 31 Oct 2005, Ralf Wildenhues wrote:
> > 
> [snip]
> > So I guess we don't want to see the read failure error from grep, since
> > we deal with it.  This slightly simpler patch should work as well, with
> > sed being greedy.  OK?
> 
> Tests fine here.

Thanks.  Applied to branch-1-5 as shown, and CVS HEAD as below.

Cheers,
Ralf

2005-10-31  Kean Johnston  <address@hidden>

        * libltdl/m4/libtool.m4 (LT_CMD_MAX_LEN): Set correctly for SCO.

Index: libltdl/m4/libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/libltdl/m4/libtool.m4,v
retrieving revision 1.29
diff -u -r1.29 libtool.m4
--- libltdl/m4/libtool.m4       31 Oct 2005 09:58:38 -0000      1.29
+++ libltdl/m4/libtool.m4       31 Oct 2005 18:52:38 -0000
@@ -1378,6 +1378,17 @@
       esac
     fi
     ;;
+  sco3.2v5*)
+    lt_cv_sys_max_cmd_len=102400
+    ;;
+  sysv5* | sco5v6* | sysv4.2uw2*)
+    kargmax=`grep ARG_MAX /etc/conf/cf.d/stune 2>/dev/null`
+    if test -n "$kargmax"; then
+      lt_cv_sys_max_cmd_len=`echo $kargmax | sed 's/.*[[       ]]//'`
+    else
+      lt_cv_sys_max_cmd_len=32768
+    fi
+    ;;
   *)
     # Make teststring a little bigger before we do anything with it.
     # a 1K string should be a reasonable start.