Date:	Sun, 14 Jan 2001 09:56:21 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT bigfoot DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Where does gcc -o foo make foo.exe
In-Reply-To:	<3A605A7C.44.7AB95C@localhost>
Message-ID:	<Pine.SUN.3.91.1010114095252.24890Q@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 Sat, 13 Jan 2001, Mark E. wrote:

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

Yes (I assume you meant /dev/env/DJDIR/bin/stubify.exe).  But I wonder 
whether we should add to this list SELFDIR/stubify.exe, where SELFDIR is 
the directory part of ld.exe's argv[0]?  That would allow ld.exe to DTRT 
even if DJGPP.ENV is not there (since DJDIR is computed by the code which 
reads DJGPP.ENV).

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

Thanks!

- Raw text -