[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SCO/bugfix patch 1 of 10: AC_LIBTOOL_SYS_MAX_CMD_LEN
From: |
Tim Rice |
Subject: |
Re: SCO/bugfix patch 1 of 10: AC_LIBTOOL_SYS_MAX_CMD_LEN |
Date: |
Mon, 31 Oct 2005 10:14:27 -0800 (PST) |
On Mon, 31 Oct 2005, Ralf Wildenhues wrote:
> Hi Kean,
>
[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.
>
> Cheers,
> Ralf
>
> > 2005-10-24 Kean Johnston <address@hidden>
> >
> > * libtool.m4(AC_LIBTOOL_SYS_MAX_CMD_LEN): Set correctly for SCO.
>
> Index: libtool.m4
> ===================================================================
> RCS file: /cvsroot/libtool/libtool/Attic/libtool.m4,v
> retrieving revision 1.314.2.116
> diff -u -r1.314.2.116 libtool.m4
> --- libtool.m4 31 Oct 2005 08:38:50 -0000 1.314.2.116
> +++ libtool.m4 31 Oct 2005 09:09:16 -0000
> @@ -738,6 +738,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
> + ;;
> *)
> # If test is not a shell built-in, we'll probably end up computing a
> # maximum length that is only half of the actual maximum length, but
>
>
>
>
--
Tim Rice Multitalents (707) 887-1469
address@hidden