From: "Mark E." <snowball3 AT bigfoot DOT com>
To: Laurynas Biveinis <lauras AT softhome DOT net>, djgpp-workers AT delorie DOT com
Date: Sat, 24 Jun 2000 16:58:59 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Bash 2.04 beta 5 released
Message-ID: <3954E8D3.16959.132E0E1@localhost>
In-reply-to: <395514A8.5044FC7A@softhome.net>
X-mailer: Pegasus Mail for Win32 (v3.12c)
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

Hello,

> Can anyone reproduce and confirm the problem? If it
> is not (I hope) reproducable, it must be a problem
> at my side, e.g. symlink-related.

I cleared my /djgpp/tmp directory (it had a bunch of RHIDE directories 
hanging around) and configured GCC. The directory was still clear afterward.

> The easiest way to reproduce is to run config.sub as
> sh config.sub i386 

I tried this too with a very recent config.sub, but still couldn't reproduce 
the problem.

You imply that you rebult Bash 2.04 with your symlink-patches, I suggest 
doing the same with the Bash 2.03 and see if the problem persists. If not, it 
suggests an incompatibility between Bash 2.04's way of handling temporary 
files and the symlink patches.

Mark