X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 17 Mar 2009 16:01:49 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] [1.7] Updated: {libtool/libltdl7}-2.2.7a-10
Message-ID: <20090317150149.GC9322@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <89694 DOT 8915 DOT qm AT web25006 DOT mail DOT ukl DOT yahoo DOT com> <49BFAD95 DOT 4000709 AT gmail DOT com> <20090317145526 DOT GA12457 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090317145526.GA12457@calimero.vinschen.de>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mar 17 15:55, Corinna Vinschen wrote:
> On Mar 17 14:03, Dave Korn wrote:
> >   I noticed that the output from 'file' has changed recently, e.g.:
> > 
> > /bin $ file -L /bin/ls.exe
> > /bin/ls.exe: MS-DOS executable PE  for MS Windows (console) Intel 80386 32-bit
> > 
> >   Maybe this will help?  Or perhaps something similar elsewhere.  Libtool uses
> > file in several ways to help it decide what it's going to build.
> > 
> > 
> > /bin $ diff -pu libtool.orig libtool
> > --- libtool.orig        2009-03-15 23:19:29.500000000 +0000
> > +++ libtool     2009-03-15 23:21:14.906250000 +0000
> > @@ -3273,6 +3273,7 @@ func_win32_libid ()
> >    *executable*) # but shell scripts are "executable" too...
> >      case $win32_fileres in
> >      *MS\ Windows\ PE\ Intel*)
> > +    *PE*\ *MS\ Windows\ *Intel*)
> >        win32_libid_type="x86 DLL"
> 
> I'm wondering how the original expression was supposed to work even
> with older file(1) versions:
> 
>   $ file-4.21 /bin/bash
>   /bin/bash: MS-DOS executable PE  for MS Windows (console) Intel 80386 32-bit
> 
> That doesn't match "*MS\ Windows\ PE\ Intel*" as far as I can see.

Either way, do you want me to take this upstream?  I'm already writing
a mail to the upstream maintainer about the apparent inability to
recognize troff files.  While I'm at it, I could ask if the string for
Win32 executables could be reverted to the old style.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/