Message-ID:	<395C8B1B.1E6B0813@softhome.net>
Date:	Fri, 30 Jun 2000 13:57:15 +0200
From:	Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer:	Mozilla 4.73 [en] (Win98; U)
X-Accept-Language:	lt,en
MIME-Version:	1.0
To:	"Mark E." <snowball3 AT bigfoot DOT com>
CC:	DJGPP Workers <djgpp-workers AT delorie DOT com>,
	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Subject:	Re: Bash 2.04 beta 5 released
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000629095911 DOT 9718K-100000 AT is>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> One possible reason for dissimilar behavior is the system
> configuration.  It might be a good idea to try to reproduce this in a
> controlled environment, like a vanilla DOS system, or compare the
> system configurations to find the differences.  For example, does
> TMPDIR point to a real disk (as opposed to RAM disk) in both cases?
> Do both systems run Windows, and which version?  Etc., etc.

Because stock bash binaries work OK here, something wrong is with
build environment. Because of this problem I've downloaded stock
binaries of following GNU utilities and replaced compiled from sources
ones (to ensure there is no partial symlink support thrown in somewhere):
bnu2951b.zip
bsh204b.zip
dif272b.zip
fil316b.zip
gcc2952b.zip
mak379b.zip
sed302b.zip
djdev from today's CVS

I've tried both using stock Makefile from your distribution and reconfiguring
sources. It didn't help.

My environment:
TMP=C:\WINDOWS\TEMP
TEMP=C:\WINDOWS\TEMP
PROMPT=$p$g
winbootdir=C:\WINDOWS
COMSPEC=C:\COMMAND.COM
CVSROOT=:pserver:lauras AT cvs DOT delorie DOT com:/cvs/djgpp
DJGPP=C:/djgpp/djgpp.env
PATH=C:/DJGPP/BIN;C:/PP/BIN/GO32V2;C:/DJGPP/GNU/EMACS/BIN;C:/UTIL/PKWARE;C:/UTIL;C:\WINDOWS;C:\WINDOWS\COMMAND
HOME=C:/Programs/CVS
windir=C:\WINDOWS
BLASTER=A220 I5 D1 T4 P330

Anything else?
Laurynas

- Raw text -