From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	djgpp-workers AT delorie DOT com
Date:	Thu, 18 Jan 2001 15:28:59 -0500
MIME-Version:	1.0
Subject:	Re: Where does gcc -o foo make foo.exe
Message-ID:	<3A670BBB.11945.B01FB8@localhost>
References:	<3A605A7C DOT 44 DOT 7AB95C AT localhost>
In-reply-to:	<Pine.SUN.3.91.1010114095252.24890Q@is>
X-mailer:	Pegasus Mail for Win32 (v3.12c)
Reply-To:	djgpp-workers 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).
> > 

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

As has already been noted, the stub is read in from a djgpp-specific routine 
inside bfd where argv[0] is not accessible. To support searching 
argv[0]/stubify or a --stub=path command line option, the code that reads in 
the stub would have to be moved to ld where argv[0] is accessible and where 
we can even add a --stub=path routine if desired. The PE linker from 
ld/emulparams/pe.em manages to pass PE specific values to its bfd routine 
like an image's base address for example.

Making all these adjustments isn't trivial so I think for now it will be 
better to add $DJDIR/bin/stubify.exe to the stub search list and then 
plot an overhaul after 2.11 is released.

Mark

- Raw text -