This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problem with NC.1.107
- From: L A Walsh <cygwin at tlinx dot org>
- To: lbmgmusic at gmail dot com
- Cc: cygwin at cygwin dot com
- Date: Fri, 13 Apr 2018 01:44:58 -0700
- Subject: Re: Problem with NC.1.107
- References: <CAE=SzZUe8O3q4hnucctrWr=wvJwHszn8XqpqgYOSG6EOxa3iaQ@mail.gmail.com> <1732290424.20180328171523@yandex.ru> <5ACC18BF.4080904@tlinx.org> <CAE=SzZX4ztqgttxtTh+O08h-4HkK3unrRm_qg573jxj5y-h1kg@mail.gmail.com>
Jay Cotton wrote:
Here is the package listing at cygwin
nc: A simple but powerful network tool (installed binaries and support
files)
2013-03-19 15:35 0 usr/
2013-03-19 15:35 0 usr/bin/
2013-03-19 15:35 24576 usr/bin/nc.exe
2013-03-19 15:35 0 usr/share/
2013-03-19 15:35 0 usr/share/man/
2013-03-19 15:35 0 usr/share/man/man1/
2013-03-19 15:30 5052 usr/share/man/man1/nc.1.gz
---
Right. It has the two files I mentioned below, and
nc.exe isn't a text file or makefile -- but is shown by the
cygwin "file" command as an executable.
You said:
I don't see the PE32+ executable (console) x86-64, for MS Windows
>>> string.
Whereas, when I used the file command, it printed out exactly
what you were searching for. Thus my assertion that your file
command is the likely culprit.
file /usr/bin/nc
>>
/usr/bin/nc: PE32+ executable (console) x86-64 (stripped to external PDB),
for MS Windows
As for the not-executable error message, have you checked,
as suggested elsewhere, whether or not you have some cheap
anti-virus installed that blocks programs that are not viruses
like 'nc'?
--
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