From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	<djgpp-workers AT delorie DOT com>
Subject:	RE: Where does gcc -o foo make foo.exe
Date:	Sun, 14 Jan 2001 10:34:27 +0100
Message-ID:	<NEBBIOJNGMKPNOBKHCGHEEJBCAAA.tim.van.holder@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
In-Reply-To:	<Pine.SUN.3.91.1010114095252.24890Q@is>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id EAA05833
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

> 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).
I believe the stub loading is done by BFD, not ld; so getting (portably) at
the path to the current executable may not be obvious.

- Raw text -