Newsgroups: comp.os.msdos.djgpp
From: tob AT world DOT std DOT com
Subject: Re: Thanks and report (Making gcc 2.8.1; help requested)
Message-ID: <EqAuLr.EI3@world.std.com>
Sender: tob AT world DOT std DOT com (Tom Breton)
Reply-To: tob AT world DOT std DOT com
Organization: BREnterprises
References: <Pine DOT SUN DOT 3 DOT 91 DOT 980322155016 DOT 12221G-100000 AT is>
Date: Tue, 24 Mar 1998 01:25:02 GMT
Lines: 26
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> writes:
> 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.
>

Done, and the problem went away. Thanks.

> > 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.

I see. Thanks.

         Tom


--
When you see a spam, just remember that a spammer is some fool who just
can't believe that if they bother a million people, they'll get fewer
than a dozen interested responses. (Copy this so more wannabe spammers see it)