Date:	Wed, 18 Mar 1998 16:10:39 +0200 (IST)
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 (Re: Making gcc 2.8.1; help requested)
In-Reply-To:	<EpzxJM.5uJ@world.std.com>
Message-ID:	<Pine.SUN.3.91.980318161021.21675I-100000@is>
MIME-Version:	1.0

On Wed, 18 Mar 1998 tob AT world DOT std DOT com wrote:

>    What happens is that bash, when running COFF image files, makes
>    go32-v2 try to call go32 and also fail to find it. Really weird. DOS
>    runs 'em fine, both the *.exe's and "go32-v2 <COFF image>". Under DOS
>    go32-v2 doesn't even try to find go32 (tested by renaming it: no
>    change)

This is some snafu specific to your system.  go32-v2 should only try
to find go32.exe if the first opcode in the COFF image it finds is
what DJGPP v1.x was producing; otherwise it runs the COFF image by
itself.  I cannot imagine how could it be in error.  Could you please
set GO32_V2_DEBUG=y in the environment, run the original Makefile
(without the $(exeext) hack) again and tell what does go32-v2 print?

> * I had to truncate the tmp-<yaddayadda> file names in the makefile so
>   move-if-changed would admit the files existed. Right, I don't have
>   long filenames. I know that.

This might be a bug in the ported source distribution.  Robert, can
you see if there's a problem here on non-LFN systems?

> * For reference by anyone who tries this in the future, you really do
>   need the latest make, make-3.761. make-3.73 won't do it.

Make 3.73 didn't support Unix-like shells.  You need 3.75 or later.
Doesn't README.dos say so?

- Raw text -