From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3685 invoked by alias); 10 Jul 2012 15:25:10 -0000 Received: (qmail 3661 invoked by uid 22791); 10 Jul 2012 15:25:09 -0000 X-SWARE-Spam-Status: No, hits=-5.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com) (209.85.160.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 10 Jul 2012 15:24:54 +0000 Received: by pbcwz7 with SMTP id wz7so430513pbc.2 for ; Tue, 10 Jul 2012 08:24:54 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.211.41 with SMTP id mz9mr69693065pbc.12.1341933894151; Tue, 10 Jul 2012 08:24:54 -0700 (PDT) Received: by 10.66.82.6 with HTTP; Tue, 10 Jul 2012 08:24:54 -0700 (PDT) In-Reply-To: References: <20120709154456.GA6696@ednor.casa.cgf.cx> <1BBEF94B6B46E54980290D150A6F2EDD20C950F5@SN2PRD0610MB396.namprd06.prod.outlook.com> Date: Tue, 10 Jul 2012 15:25:00 -0000 Message-ID: Subject: Re: Inconsistence on file operation when the name already exists with exe extension From: Earnie Boyd To: notstop@users.sourceforge.net, cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-07/txt/msg00135.txt.bz2 On Tue, Jul 10, 2012 at 4:34 AM, Aaron Schneider wrote: > You're right that cygwin shell tries to emulate bash, I just twisted things. > You're still wrong. Cygwin is a POSIX library for Windows. Bash is a shell capable of being built with that POSIX library for use on Windows but it isn't an emulation of Bash, it *is* Bash. Other shells available on *nix is also available for Cygwin. > The problem is that in unix executables don't have extension but they actually do in cygwin so I think that's the root of the problem. > They don't need one in Cygwin either; as a matter of fact it was an addition to binutils in the second generation of Cygwin that added the .exe to the executable because it was more natural for Windows and Windows at the time wouldn't execute the binary without the .exe extension. > Probably compiling binaries under cygwin without the exe extension, like unix, is not an alternative, or is it? Cygwin may detect if it is executable checking if it's PE format; if it is perl script. Just check if file is present in path or run. /file False. It is wholly possible, you just have to pass the correct flags to the linker process. Current windows versions since at least XP and maybe before would run files that did not contain a .exe extension. -- Earnie -- https://sites.google.com/site/earnieboyd -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple