public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: checking cyg version (was Re: GNU make losing jobserver tokens)
Date: Tue, 22 Mar 2022 21:58:41 +0000	[thread overview]
Message-ID: <20220322215841.v34izvcsqxqikpzr@lucy.dinwoodie.org> (raw)
In-Reply-To: <623A25BA.5030006@tlinx.org>

On Tue, Mar 22, 2022 at 12:38:34PM -0700, L A Walsh wrote:
> On 2022/03/21 08:09, Ken Brown wrote:
> > 
> > For starters, is your Cygwin installation up to date?  Cygwin's internal
> > implementation of pipes was overhauled starting with cygwin-3.3.0.
> How does one check the version of cygwin?  I've updated cygwin files this
> year,
> but if I use cygcheck -V, I only see cygwin-3.2, which looks to be from last
> year.

Unless you're doing something very odd, that implies you're running a
version that's just under a year old, and which won't include the pipe
changes Ken is referring to.

> Is that they right way to check the cygwin version?

Not really: `cygcheck -V` is just reporting the version of cygcheck that
you have installed.  That should normally match the version of the core
"cygwin" package, which also includes the cygwin1.dll library that makes
everything else possible.  However "the version of Cygwin" isn't a
meaningful concept: a Cygwin installation is made up of many parts, each
of which has its own version number.  There's more detail at
https://cygwin.com/faq/faq.html#faq.what.version

  reply	other threads:[~2022-03-22 21:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 14:28 GNU make losing jobserver tokens Magnus Ihse Bursie
2022-03-21 15:09 ` Ken Brown
2022-03-22  6:54   ` Noel Grandin
2022-03-22 17:52     ` GNU make losing jobserver tokens in pipes Brian Inglis
2022-03-22 19:38   ` checking cyg version (was Re: GNU make losing jobserver tokens) L A Walsh
2022-03-22 21:58     ` Adam Dinwoodie [this message]
2022-03-22 23:06     ` Mark Geisert
2022-03-23 17:47       ` Samuel Lelièvre
2022-03-23  6:24 ` GNU make losing jobserver tokens Roumen Petrov
2022-04-01  8:45 ` Takashi Yano
2022-04-27 14:13   ` Takashi Yano
2022-04-28 13:42     ` Ken Brown
2022-04-28 14:09       ` Corinna Vinschen
2022-04-28 15:01         ` Takashi Yano
2022-04-28 15:32           ` Corinna Vinschen
2022-04-29  9:10             ` Takashi Yano
2022-04-30 21:51               ` Ken Brown
2022-05-01  0:51                 ` Takashi Yano

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=20220322215841.v34izvcsqxqikpzr@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --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).