public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: lbmgmusic@gmail.com
Cc: cygwin@cygwin.com
Subject: Re: Problem with NC.1.107
Date: Fri, 13 Apr 2018 08:45:00 -0000	[thread overview]
Message-ID: <5AD06E0A.6010103@tlinx.org> (raw)
In-Reply-To: <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

  parent reply	other threads:[~2018-04-13  8:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28  7:09 Jay Cotton
2018-03-28 14:05 ` Marco Atzeri
2018-03-28 14:20 ` Andrey Repin
2018-04-10  1:52   ` L A Walsh
2018-04-10  4:12     ` Jay Cotton
2018-04-10  5:54       ` Marco Atzeri
2018-04-13  8:45       ` L A Walsh [this message]
2018-04-13 12:29         ` Brian Inglis

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=5AD06E0A.6010103@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@cygwin.com \
    --cc=lbmgmusic@gmail.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).