Date:	Sun, 24 Jun 2001 11:02:39 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp-workers AT delorie DOT com
Subject:	Re: Compile gcc 3.0
In-Reply-To:	<RMbZ6.73260$ru2.21459476@typhoon.southeast.rr.com>
Message-ID:	<Pine.SUN.3.91.1010624110205.13700P-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 24 Jun 2001, jonathan bailey wrote:

> 1. At some point during configure, I see a line that says
>     'Determining maximum length of command line input'
>     or something close to this statement, after a minute or so,
>     the computer either locks up completly, or if I'm lucky I get a
>     error message stating that a invalid opcode error has occured,
>     either way I have to reboot the computer.

Did someone submit some changes to the libtool maintainers to fix this
problem?  I think we should do that ASAP, since DJGPP v2.04 is still
far away, so we will have to live with the problem for some time.
Meanwhile, more and more GNU projects start using this version of
libtool.

I think the only reasonable way to fix that would be for libtool to
skip this test completely for DJGPP, and use a static limit (like
12KB) instead.  That's because even if we fix glob to not blow away
the stack for large argv[] elements, the computed limitation--1MB--is
meaningless and even dangerous (in case programs are invoked directly,
not via Bash).

- Raw text -