Date: Mon, 2 Nov 1998 10:04:38 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Ian Miller cc: djgpp AT delorie DOT com Subject: Re: DJGPP 2.02 Beta 981027 In-Reply-To: <71ifot$b9n@news3.force9.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com On Sun, 1 Nov 1998, Ian Miller wrote: > groff-1.10 > > The install target very irritatingly installed the executables > *without* the .exe extension. I think this is a side-effect of the feature in the latest Binutils port, whereby "gcc -o foo" produces `foo' that is a stubified executable. The DJGPP port of GNU install (from Fileutils) generates a stubified executable with a .exe extension on the fly when the Makefile says e.g. "ginstall foo c:/djgpp/bin/foo", but it will only do so if `foo' is a raw COFF image. Since GCC 2.8.1 and Binutils 2.8.1 produce stubified executable, ginstall doesn't do that. I was never in fond of this change in Binutils, and I'm even less in fond of it now, because I'm not sure whether there's a simple fix that will resurrect this feature of ginstall. (An alternative would be to edit the Makefiles so that the .exe suffix is explicit in the install targets. But this is against the tradition of DJGPP development that tries hard to change as little as possible by making such Unixisms magically work .) > But apart from that the build, test, and install went well. Thanks for testing this.