From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dave Korn" To: "gcc-patches" Subject: Re: Unreviewed patch Date: Sun, 11 Feb 2001 16:37:00 -0000 Message-id: <005101c0948b$efa42190$7994fd3e@ubik> References: <20010211124439.1117.qmail@lauras.lt> <20010211101149.C14114@redhat.com> X-SW-Source: 2001-02/msg00629.html ----- Original Message ----- From: "Richard Henderson" Sent: Sunday, February 11, 2001 6:11 PM > On Sun, Feb 11, 2001 at 02:44:39PM +0200, Laurynas Biveinis wrote: > > http://gcc.gnu.org/ml/gcc-patches/2001-01/msg01085.html > > > > It's a compiler driver fix for DJGPP, so gcc no longer > > errorneously appends executable suffix to output file. > > I'd rather all the dos-based systems work the same way > wrt extensions. And really those are the only systems > with extensions still. There's still a problem with the driver mechanism, because the .exe extension is attached or not depending on the host machine type, rather than the target machine type. This is wrong-but-right-by-accident on a native compiler, and just plain wrong on a cross compiler (I ran into it on the vxworks port). FWIW, I've made a similar patch in my local source tree; my one allows the target header to provide definitions TARGET_OBJECT_SUFFIX and TARGET_EXECUTABLE_SUFFIX which override OBJECT_SUFFIX and EXECUTABLE_SUFFIX in the part of the driver that generates output files (but not the parts of the driver that search for files on the host). However, IMO the most properly correct way to do it would be for configure to work out the appropriate extensions to use for host and target files. I haven't looked at it any further than that because I don't understand auto* stuff. DaveK