From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Sat, 13 Jan 2001 11:52:09 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Where does gcc -o foo make foo.exe
Message-ID: <3A604169.19279.186908@localhost>
In-reply-to: <2110-Sat13Jan2001093422+0200-eliz@is.elta.co.il>
References: <3A5F49FE DOT 11625 DOT 45D878 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
Precedence: bulk

> > Right. But DJGPP overrides LINK_COMMAND_SPEC in gcc's djgpp.h to use 
> > djgpp.djl (which sets the target to coff-go32) and then call stubify on the 
> > result. Any chance we can now finally agree to dispense with this?
> 
> Why would we want to dispense with that?

It would cut out an unneccessary step during linking. The binutils linker 
script would then be the default so we'd no longer rely on the DJGPP script 
which omits some features because of the neccessity to be compatible with 
earlier binutils versions.

Mark