bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FYI: sys_max_cmd_len for BSDs


From: Ralf Wildenhues
Subject: FYI: sys_max_cmd_len for BSDs
Date: Fri, 1 Apr 2005 11:30:30 +0200
User-agent: Mutt/1.4.1i

* Peter O'Gorman wrote on Fri, Apr 01, 2005 at 07:44:01AM CEST:
> Ralf Wildenhues wrote:
> | * Mike Stump wrote on Wed, Mar 30, 2005 at 12:57:59AM CEST:
> |
> |>How about this one...  The /4 comes from the old code in ltconfig
> |>that did:
*snip*
> |>In the end it was 3/4 the original value..
> |
> | Yes, I looked around in the old code a bit, and think you are right
> | about this.  (16384 seems ok for C++ to me.)  The patch to the current
> | code[1] bears no obvious argument towards 0.25 vs 0.75.
> 
> This is fine with me, please apply.

Thanks.  I have applied the following patch to all three branches
(patch to HEAD/branch-2-0 shown below).

Regards,
Ralf

2005-04-01  Mike Stump  <address@hidden>

        * m4/libtool.m4 (LT_CMD_MAX_LEN) [ netbsd, freebsd, openbsd,
        darwin, dragonfly]: Use 3/4 of argmax, instead of 1/4.

Index: m4/libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/m4/libtool.m4,v
retrieving revision 1.177
diff -u -r1.177 libtool.m4
--- m4/libtool.m4       28 Mar 2005 09:32:59 -0000      1.177
+++ m4/libtool.m4       1 Apr 2005 09:25:31 -0000
@@ -1167,6 +1167,7 @@
     fi
     # And add a safety zone
     lt_cv_sys_max_cmd_len=`expr $lt_cv_sys_max_cmd_len \/ 4`
+    lt_cv_sys_max_cmd_len=`expr $lt_cv_sys_max_cmd_len \* 3`
     ;;
   osf*)
     # Dr. Hans Ekkehard Plesser reports seeing a kernel panic running configure




reply via email to

[Prev in Thread] Current Thread [Next in Thread]