Date:	Sun, 22 Mar 1998 15:50:36 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	tob AT world DOT std DOT com
cc:	djgpp AT delorie DOT com
Subject:	Re: Thanks and report (Making gcc 2.8.1; help requested)
In-Reply-To:	<Eq3DE7.JAy@world.std.com>
Message-ID:	<Pine.SUN.3.91.980322155016.12221G-100000@is>
MIME-Version:	1.0

On Fri, 20 Mar 1998 tob AT world DOT std DOT com wrote:

> I tried it that way, and it still says the same: "go32/v1: cannot find
> v1's go32.exe". Then I looked for the string GO32_V2_DEBUG in
> go32-v2.exe and it's nowhere in the executable, so it may not reading
> that environment variable at all.
> 
> However, while doing that I discovered something about the problem:
> "go32.exe" is misinstalled on my system (legacy, long story). It is
> *also* a v2, so maybe it gets called, in its turn looks for something to
> run v1, of course can't find it, and dies.

You are using an old and buggy version of go32-v2.exe, from DJGPP
v2.0.  Please overwrite it with go32-v2.exe from DJGPP v2.01 and see
if the problem gows away.

> I still don't know why or how bash makes go32-v2 look for a v1 in the
> first place when DOS doesn't have the problem. I suppose I can live
> without knowing that.

It's tricky.  When go32-v2 is invoked from another DJGPP program, it
gets the command-line arguments differently than from the DOS prompt.
go32-v2.exe from v2.0 is incompatible with DJGPP v2.01; don't use it,
or you *will* see such subtle bugs.

- Raw text -