From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32676 invoked by alias); 10 Jul 2012 16:23:25 -0000 Received: (qmail 32653 invoked by uid 22791); 10 Jul 2012 16:23:23 -0000 X-SWARE-Spam-Status: No, hits=2.7 required=5.0 tests=AWL,BAYES_00,BOTNET,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from vms173021pub.verizon.net (HELO vms173021pub.verizon.net) (206.46.173.21) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 10 Jul 2012 16:23:06 +0000 Received: from [192.168.1.231] ([unknown] [108.7.54.123]) by vms173021.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0M6Y00HR5DHQ4SFP@vms173021.mailsrvcs.net> for cygwin@cygwin.com; Tue, 10 Jul 2012 11:22:44 -0500 (CDT) Message-id: <4FFC56CF.8090202@cygwin.com> Date: Tue, 10 Jul 2012 16:23:00 -0000 From: "Larry Hall (Cygwin)" Reply-to: cygwin@cygwin.com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-version: 1.0 To: cygwin@cygwin.com Subject: Re: Inconsistence on file operation when the name already exists with exe extension References: <20120709154456.GA6696@ednor.casa.cgf.cx> <1BBEF94B6B46E54980290D150A6F2EDD20C950F5@SN2PRD0610MB396.namprd06.prod.outlook.com> In-reply-to: Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit 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/msg00137.txt.bz2 On 7/10/2012 11:24 AM, Earnie Boyd wrote: > 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. All true. And all discussed before, as Chris pointed out earlier. Earnie and others are being very helpful to the OP by reviewing this stuff again. It's great to ask questions and explore boundaries but what's better is to explore new boundaries and ask new questions. I'd also encourage that those interested in this area (and I am certainly one) review what's been said on this subject so far so that any further discussions will be engaging for all. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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