From: "Nellis, Kenneth" <Kenneth.Nellis@conduent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: i686-w64-mingw32-gcc -fstack-protector-strong
Date: Fri, 08 Sep 2017 21:09:00 -0000 [thread overview]
Message-ID: <BN6PR2001MB1074193116FC407CB190C166F1950@BN6PR2001MB1074.namprd20.prod.outlook.com> (raw)
In-Reply-To: <CAD8GWsu53ZtB5exta8vmpAJZiNsvAi2xKK0KKctq-hiaW5Fsfw@mail.gmail.com>
> From: Lee
> ...
> Was there ever a man page for cygcheck? I remember looking at one,
> but maybe I it was https://cygwin.com/cygwin-ug-net/cygcheck.html ??
> $ man cygcheck
> No manual entry for cygcheck
>
> $ info cygcheck
> info: No menu item 'cygcheck' in node '(dir)Top'
Both man and info work for me:
$ man cygcheck | head
CYGCHECK(1) Cygwin Utilities CYGCHECK(1)
NAME
cygcheck - List system information, check installed packages, or query package database
SYNOPSIS
cygcheck [-v] [-h] PROGRAM
cygcheck -c [-d] [PACKAGE]
cygcheck -s [-r] [-v] [-h]
cygcheck -k
$ info cygcheck | head
info: No menu item 'cygcheck' in node '(dir)Top'
CYGCHECK(1) Cygwin Utilities CYGCHECK(1)
NAME
cygcheck - List system information, check installed packages, or query package database
SYNOPSIS
cygcheck [-v] [-h] PROGRAM
cygcheck -c [-d] [PACKAGE]
cygcheck -s [-r] [-v] [-h]
cygcheck -k
$
--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
next prev parent reply other threads:[~2017-09-08 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 14:15 Lee
2017-09-08 15:04 ` Marco Atzeri
2017-09-08 18:53 ` Lee
2017-09-08 19:25 ` Marco Atzeri
2017-09-08 20:01 ` Lee
2017-09-08 20:10 ` Marco Atzeri
2017-09-08 21:08 ` Lee
2017-09-08 22:34 ` Yaakov Selkowitz
2017-09-08 23:10 ` Lee
2017-09-08 21:09 ` Nellis, Kenneth [this message]
2017-09-08 21:42 ` Lee
2017-09-08 23:01 ` Steven Penny
2017-09-08 23:22 ` Lee
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=BN6PR2001MB1074193116FC407CB190C166F1950@BN6PR2001MB1074.namprd20.prod.outlook.com \
--to=kenneth.nellis@conduent.com \
--cc=cygwin@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).