Date: Fri, 19 Jan 2001 12:10:26 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Mark E." Message-Id: <1438-Fri19Jan2001121025+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 CC: djgpp-workers AT delorie DOT com In-reply-to: <3A670BBB.11945.B01FB8@localhost> (snowball3@bigfoot.com) Subject: Re: Where does gcc -o foo make foo.exe References: <3A605A7C DOT 44 DOT 7AB95C AT localhost> <3A670BBB DOT 11945 DOT B01FB8 AT localhost> 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 Precedence: bulk > From: "Mark E." > Date: Thu, 18 Jan 2001 15:28:59 -0500 > > > 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. Tim suggested to look at __crt0_argv, which is a global variable. > 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. I agree; as long as we don't toss djgpp.djl, there's no urgency to make these changes.