Subject: Re: Determining the "maximum length of command line argument"
To: Martin Weber <Ephaeton@gmx.net>
From: Ron Roskens <roskens@elfin.net>
List: tech-pkg
Date: 01/23/2004 21:49:05
* Martin Weber <Ephaeton@gmx.net> [2004-01-24 00:05:34 +0100]:

> On Fri, Jan 23, 2004 at 05:30:55PM +0000, Johnny C. Lam wrote:
> > Newer GNU configure scripts try to determine the maximum length of command
> > line arguments by trying trying to echo longer and longer strings until
> > it find the longest string that it can echo (65536 on my i386 box).  
> > (...) How should we determine this on NetBSD systems?
> > If it's exceptionally variable, can we arbitrarily choose a reasonble
> > default for various MACHINE_PLATFORMs?
> 
> 
> P L E A S E ! :) Nothing like going into a meta pkg and typing make install
> there on a sparc, and see each dependancy hang five minutes (not kidding :)
> in that step. Over and over again.
> 
> Maybe there should be a global cache in pkgsrc for configure run results.
> That way it wouldn't be required to set at sometime in advance, yet configure
> runs over time would add the pieces missing.

You can do this already. Set the value for the variable inside
${LOCALBASE}/etc/config.site, and configure will automagically pick it up.

ie:
    roskens@hysteria$ cat /usr/pkg/etc/config.site
    lt_cv_sys_max_cmd_len=65536

Ron