X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date:	Sun, 9 Dec 2001 11:37:33 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Andrew Cottrell <acottrel AT ihug DOT com DOT au>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Why do there appear to be two stubs in some files?
In-Reply-To:	<006d01c18068$f173b250$0102a8c0@acceleron>
Message-ID:	<Pine.SUN.3.91.1011209113659.13320J-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 9 Dec 2001, Andrew Cottrell wrote:

> I diffed the 2.04 stub.h against the go32stub.h and there were allot more
> changes then when I compared the 2.03 sub.h against the go32stub.h. The
> changes in 2.03 v's go32stub.h are expected due to the date and time info in
> the stub.
> 
> The stub.asm file changed in 2.04 and as such does this mean that so should
> go32stub.h in Binutils when 2.04 is released?

It's a good idea to update Binutils with the latest stub whenever a
new DJGPP release is done.  This has been discussed in the past, at
which time I suggested to change the Binutils build procedure to
automatically pick up the latest stub from the installed djdev.
Others didn't feel it was important enough to do this, so it didn't
happen.

However, it is not critically important to have the bleading-edge stub
in Binutils: as I just mentioned in another thread, the setting of
GO32STUB environment variable in DJGPP.ENV forces Binutils to use the
stub from stubify.exe.  So the stub built into Binutils programs is
only important for installations where stubify.exe is not available--a
fairly rare phenomenon, one would hope ;-)

- Raw text -