This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Fw: Not a cygport problem [Was: Re: Problem with 575 man pages -- cygport problem?]
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: The Vulgar and Backwardly-Incompatible Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
- Date: Tue, 17 Mar 2009 13:59:06 +0000
- 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>
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
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