From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31398 invoked by alias); 17 Mar 2009 13:49:37 -0000 Received: (qmail 31389 invoked by uid 22791); 17 Mar 2009 13:49:36 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-ew0-f172.google.com (HELO mail-ew0-f172.google.com) (209.85.219.172) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 17 Mar 2009 13:49:25 +0000 Received: by ewy20 with SMTP id 20so59976ewy.2 for ; Tue, 17 Mar 2009 06:49:22 -0700 (PDT) Received: by 10.216.25.82 with SMTP id y60mr41290wey.4.1237297761992; Tue, 17 Mar 2009 06:49:21 -0700 (PDT) Received: from ?82.6.108.62? (cpc2-cmbg8-0-0-cust61.cmbg.cable.ntl.com [82.6.108.62]) by mx.google.com with ESMTPS id 6sm9148566nfv.24.2009.03.17.06.49.21 (version=SSLv3 cipher=RC4-MD5); Tue, 17 Mar 2009 06:49:21 -0700 (PDT) Message-ID: <49BFACAA.5040106@gmail.com> Date: Tue, 17 Mar 2009 13:49:00 -0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: The Vulgar and Backwardly-Incompatible Cygwin-Talk Maiming List Subject: Fw: Not a cygport problem [Was: Re: Problem with 575 man pages -- cygport problem?] References: <49BDE52A.80100@veritech.com> <20090316131743.GC23977@ednor.casa.cgf.cx> <49BE6A68.9040705@veritech.com> <49BEF96D.8060809@cwilson.fastmail.fm> <2bf229d30903161912i582e954q91ad25a56c82b262@mail.gmail.com> <49BF2EDD.3040606@cwilson.fastmail.fm> In-Reply-To: <49BF2EDD.3040606@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-talk-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-talk-owner@cygwin.com Reply-To: The Vulgar and Unprofessional Cygwin-Talk List Mail-Followup-To: cygwin-talk@cygwin.com X-SW-Source: 2009-q1/txt/msg00067.txt.bz2 Charles Wilson wrote: > It depends on which version of 'file' you are using. On cygwin-1.7, the > current version of file: > > $ file -version > file-5.00 > > reports ASCII text. > > On cygwin-1.5, the current version of file > > $ file -version > file-4.21 > > reports ASCII troff. Is it just me, or does anyone else think that upstream has a slightly odd attitude towards backward compatibility? *executable*) # but shell scripts are "executable" too... case $win32_fileres in *MS\ Windows\ PE\ Intel*) win32_libid_type="x86 DLL" ;; esac $ file /bin/cyggcc_s-1.dll /bin/cyggcc_s-1.dll: PE32 executable for MS Windows (DLL) (console) Intel 80386 32-bit ~ $ file /bin/cyggcc_s-1.dll /bin/cyggcc_s-1.dll: MS-DOS executable PE for MS Windows (DLL) (console) Intel 80386 32-bit @_______. . ( /"\ ||--||(___) '" '"'---' ~ $ cheers, DaveK