X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Matthew Woehlke Subject: Re: [ANNOUNCEMENT] Updated: cygwin-1.5.22-1 Date: Thu, 16 Nov 2006 10:06:15 -0600 Lines: 28 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.0 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Champ Mendis wrote: > I reinstalled the above Cygwin version. But when I run the file it > behaves as follow, > > $ ./sensor > /sensor: ./sensor: cannot execute binary file > cmendis AT Ranmen_Dell ~/simsens-5.0 > $ rm sensor <-REMOVED AS ADVISED BEFOFRE > cmendis AT Ranmen_Dell ~/simsens-5.0 > $ ./sensor > cmendis AT Ranmen_Dell ~/simsens-5.0 > $ ./sensor > cmendis AT Ranmen_Dell ~/simsens-5.0 > $ ./sensor cmendis AT Ranmen_Dell ~/simsens-5.0 When was the last time you updated? A while back a change was made w.r.t. handling of .exe's (which Cygwin treats as 'missing the extension' in some instances). My guess is you have a 'sensor.exe' that is executable, and had a 'sensor' that was not. So when you did 'rm sensor', you removed 'sensor', and then when you do './sensor' you are running 'sensor.exe'. -- Matthew "What's Cygwin?" you ask. 'Tis mostly absurd software Concerning hippos. -- 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/