delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | djgpp-workers AT delorie DOT com |
Date: | Fri, 12 Jan 2001 18:16:30 -0500 |
MIME-Version: | 1.0 |
Subject: | Re: Where does gcc -o foo make foo.exe |
Message-ID: | <3A5F49FE.11625.45D878@localhost> |
In-reply-to: | <200101122255.RAA15943@envy.delorie.com> |
References: | <20010112223359 DOT 497 DOT qmail AT lauras DOT lt> |
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 |
> > You need the latest linker too. The stub format is the default output > format for the linker. This was done back when bfd learned how to > read stubbed exes (objdump, nm, etc). 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? Mark
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |