From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: The Vulgar and Backwardly-Incompatible Cygwin-Talk Maiming List
<cygwin-talk@cygwin.com>
Subject: Fw: Not a cygport problem [Was: Re: Problem with 575 man pages -- cygport problem?]
Date: Tue, 17 Mar 2009 13:49:00 -0000 [thread overview]
Message-ID: <49BFACAA.5040106@gmail.com> (raw)
In-Reply-To: <49BF2EDD.3040606@cwilson.fastmail.fm>
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
parent reply other threads:[~2009-03-17 13:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <49BF2EDD.3040606@cwilson.fastmail.fm>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49BFACAA.5040106@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).