Date: Tue, 18 Jul 2000 10:23:29 +0200
From: Laszlo Molnar <laszlo DOT molnar AT eth DOT ericsson DOT se>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: djgpp-workers AT delorie DOT com
Subject: Re: DJGPP problem executing a script
Message-ID: <20000718102328.U772@libra.eth.ericsson.se>
References: <20000717140529 DOT R772 AT libra DOT eth DOT ericsson DOT se> <Pine DOT SUN DOT 3 DOT 91 DOT 1000717154519 DOT 7821B-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <Pine.SUN.3.91.1000717154519.7821B-100000@is>; from eliz@is.elta.co.il on Mon, Jul 17, 2000 at 03:49:34PM +0300
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
Precedence: bulk

On Mon, Jul 17, 2000 at 03:49:34PM +0300, Eli Zaretskii wrote:
> > Ok, perl 5.6 builds nicely using djdev203 and gcc2952.
> Did you also fix the problem with exit status of subordinate programs
> which wasn't shifted 8 bits to the left?  (This causes one of the tests
> from the GNU Make test suite to fail, unless the test script is tweaked.)

IIRC, I fixed a problem with return codes some times ago. But to be
sure, could you send me a small test case for the problem you observed?

> > However I had a
> > problem with bash 2.03: when I run the test suite it just stopped on a
> > file - the first 7 subtests of 25 was OK, then execution is stuck in
> > the 8th test until I pressed Ctrl-C.
> Does this always happen with the 8th script, or only with the particular
> script which happens to be the 8th in the original order?  In other
> words, what happens if you remove the first test?

It happens in a particular script.

> Also, does that happen on DOS or Windows (if the latter, it might be a
> problem with resource leaks).

Plain DOS 6.22.

> > Bash 1.14.7.2 worked fine. Maybe I
> > should wait for bash 2.04...
> There's a beta available that you should be able to try.  Mark announced
> it here in the past.

bash 2.04 b5 seems to solve the lockup problem. HOwever it has another
problem: when I start configure.bat I usually use the "-dEs" command line
switch to make the configure process non-interactive. But this does not
work with bash 2.04 - it wants me to press ENTER 1E6 times...

Laszlo