Date: Mon, 23 Nov 1998 17:08:07 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Ignacio García Pérez <igp AT vlc DOT servicom DOT es>
cc: djgpp AT delorie DOT com
Subject: Re: v2.81 and PMODE
In-Reply-To: <36595d82.9583266@crispin>
Message-ID: <Pine.SUN.3.91.981123165712.24468D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id KAA07205
Reply-To: djgpp AT delorie DOT com


On Mon, 23 Nov 1998, Ignacio García Pérez wrote:

> So far, I've run GCC in verbose mode, and I see that it always
> executes STUBIFY in order to append the default stub to the program. I
> thought that  I find the way to avoid this last step, I could then add
> the PMODE stub, but found no way to tell GCC not to run STUBIFY.

Short answer:  Use the program exe2coff (it comes with djdev201.zip and 
should be already in your bin subdirectory) to extract the raw COFF image 
from the stubified executable produced by GCC 2.8.1.  Then attach the 
PMODE stub as you did before.

Longer answer: This is due to a change in the djgpp.djl linker script 
supplied with GCC 2.8.1.  It instructs GCC to produce a stubified 
executable rather than a raw COFF file, by specifying coff-go32-exe as 
the default output format.

So, apart from the above solution, you could also edit djgpp.djl and 
replace coff-go32-exe with coff-go32.  (However, messing with djgpp.djl 
is not recommended.)

Note that if you upgraded to Binutils 2.8.1 as well, the linker there has 
coff-go32-exe as its default output as well (I think), so it might also 
be part of the puzzle.