This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: distinguishing cygwin from mingw binaries
- From: "Nellis, Kenneth" <Kenneth dot Nellis at conduent dot com>
- To: Hans-Bernhard Bröker <HBBroeker at t-online dot de>, "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Tue, 11 Jul 2017 14:20:04 +0000
- Subject: RE: distinguishing cygwin from mingw binaries
- Authentication-results: sourceware.org; auth=none
- Authentication-results: t-online.de; dkim=none (message not signed) header.d=none;t-online.de; dmarc=none action=none header.from=conduent.com;
- References: <c9972edc-e767-c692-ce3f-9d577ddfc130@t-online.de>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
From: Hans-Bernhard Bröker
> That's a bit too rough. Something like
>
> cygcheck ./foo.exe | grep cygwin1.dll
> or ldd ./foo.exe | grep cygwin1.dll
>
> would be more precise.
Appreciate the improved tests. Thanx!
> > One of my wishes for Cygwin is for the "file" command to make the
> distinction.
>
> Well, SHTDI. IOW: please don't feel as if anybody were keeping you from
> constructing a 'file' rule that achieves that, and offering it to the
> public. ;-)
Of course. Just expressing a wish in case someone with more know-how
than I has their interest piqued by the idea.
--Ken Nellis
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple