Improving maximum command line length detection (Was: Re: [PATCH] Removal of obsolete AmigaOS support)

[Dalibor Topic]

Bob Friesenhahn wrote:
> On Tue, 7 Oct 2003, Gary V. Vaughan wrote:
>
>
> > Dalibor Topic wrote:
> >
> > > The major problem right now in running libtool 1.5 plus amigaos patches
> > > from CVS on m68k based machines (amigaos, or not) is the very inefficent
> > > check for maximum allowed variable length, that can take up to an hour,
> > > or more.
> >
> > Why not `export lt_cv_sys_max_cmd_len=16384', or some other value you know
> > works before running configure?  Or put it in the system-wide cache...
>
>
> At one point in time, someone (probably Dalibor Topic) suggested
> implementing an alternative algorithm which requires fewer iterations.
> I think it was also suggested that the starting point of the algorithm
> be set to just below the known worst-case system so it doesn't take
> long to find the limit.
>
> Clearly there are more sophisticated algorithms that will find the
> limit faster.
>
> Unfortunately, a patch was never submitted ...

Yep, that was me. I'll try to write a patch now, given that kaffe 1.1.2 
has been just released, and I can now try to give back a little time to 
projects that have given so much to us. Thanks for libtool!

Now, back to the (new) topic: I've proposed the following algorithm:
http://www.mail-archive.com/address@hidden/msg03888.html
ammended here: http://www.mail-archive.com/address@hidden/msg03893.html

there were no replys on the ammended method. If anyone objects to me 
putting in an 8K test string into libtool's libtool.m4 please do it now, 
before I start learning m4 ;)

cheers,
dalibor topic