Date: Thu, 29 Jul 1999 11:08:38 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Problems with latest Bash
In-Reply-To: <199907281417.OAA90802@out1.ibm.net>
Message-ID: <Pine.SUN.3.91.990729110801.25908M-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 28 Jul 1999, Mark E. wrote:

> >  - DOS_TEST_HACK=y seems to cause "test -f" to fail and/or crash in
> >    some cases.
> 
> I found the problem and it's so bad I can't believe I didn't run
> into it myself, especially since I've been configuring Binutils from
> CVS periodically. Oh well.

Since it looks like a NULL pointer dereference, Windows probably
simply lets you get away with it.

> How about just DOS_TEST_F so people don't think 'test -x' is
> affected by this variable?

Whatever you see fit.  Just don't put HACK into it ;-).