From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	djgpp-workers AT delorie DOT com
Date:	Sat, 13 Jan 2001 13:39:08 -0500
MIME-Version:	1.0
Subject:	Re: Where does gcc -o foo make foo.exe
Message-ID:	<3A605A7C.44.7AB95C@localhost>
In-reply-to:	<9628-Sat13Jan2001195838+0200-eliz@is.elta.co.il>
References:	<3A604169 DOT 19279 DOT 186908 AT localhost> (snowball3 AT bigfoot DOT com)
X-mailer:	Pegasus Mail for Win32 (v3.12c)
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

>   - the stub used to produce the .exe program should be the same stub
>     distributed with the installed djdev (I didn't forget the GO32STUB
>     feature, I just don't think it's reliable enough, because it
>     depends on DJGPP.ENV).

To locate the stub, the current order is GO32STUB, STUB, then the builtin 
stub. Would changing the order to GO32STUB, STUB, "/dev/env/bin/stubify.exe", 
and builtin stub solve this for you?

> It would also be nice to solve the problem with extra 2KB of garbage
> in the executables produced by ld.exe, but that's a minor nuisance
> (and maybe it's already solved, I don't remember).

An attempt by someone (I forget now who) tried  generic fix, but it was 
refused. The bnu210b.zip solves it in a DJGPP specific way. I'll take another 
look at this soon.

Mark

- Raw text -