Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <41C9F350.5050904@familiehaase.de> Date: Wed, 22 Dec 2004 23:21:04 +0100 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; de-AT; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: "Jeremy C. Reed" CC: cygwin AT cygwin DOT com Subject: Re: cp and "are the same file" References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Jeremy C. Reed wrote: > On Sat, 18 Dec 2004, Igor Pechtchanski wrote: > > >>>The suffix is required on Win9x, AFAIK, so this is not a viable route. >> >>That said, I believe the OP didn't request that gcc not produce .exe files >>by default, only how can *he* make gcc not produce the .exe suffix. What >>you have to do is add a "." after the output (-o) filename[*]. Some >>projects define EXEEXT (or EXESUFFIX), so setting that to "." in yours >>could be all you need. > > > Sorry that will not work for me. I am working with over 5000 build > mechanisms. I don't want to setup wrappers and other patches to add a > period hack after the output filename. > > Jeremy C. Reed PTA, please provide a patch (tested) which adds a flag to gcc on Cygwin to disable the creation of the suffix. However, you'll have to add this flag to your 50000 mechanisms as well, so maybe it would be easier for you to rebuild gcc with a completely removed suffix mechanism. BTW, I still cannot see the point why you don't want to use it as is, what is the actual problem with the suffix? Was it just the problem with cp and other tools? Why don't try to enable the tools you need instead of trying to disable features in gcc? Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/