public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: error: CYGWIN_NT-10.0-x86_64 is not supported (yet?) on Windows 10
Date: Sun, 24 Apr 2022 11:08:28 -0600	[thread overview]
Message-ID: <0ce7bb8a-af66-bf3c-e607-09cb20344271@SystematicSw.ab.ca> (raw)
In-Reply-To: <MN2PR11MB46950678BB5150B2CE71E8BCD2F99@MN2PR11MB4695.namprd11.prod.outlook.com>

On 2022-04-24 08:02, John Balkunas wrote:
> Hello,
> 
> I installed Cywin64 Terminal so that I can compile chrony-4.2 for use with Windows 10 Pro 64-bit. I used the Cygwin Setup program/installer named setup-x86_64.exe for 64 bit Windows.  The install appeared to go well.  After the install, from within the Cywin64 Terminal, I see the following 3 results:
> 
> Command: "cygcheck -V"
> Result:
> cygcheck (cygwin) 3.3.4
> System Checker for Cygwin
> Copyright (C) 1998 - 2022 Cygwin Authors
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> Command: "gcc --version"
> Result:
> gcc (GCC) 11.2.0
> Copyright (C) 2021 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> Command: "g++ --version"
> Result:
> g++ (GCC) 11.2.0
> Copyright (C) 2021 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> Thus, this leads me to think everything is ready to go on my Win10 machine for compiling.  However, when I switch to the directory I unpacked the chrony-4.2 to and run the "./configure" command (I used no switches) from within the Cygwin64 Terminal I see the following:
> 
> Command: "./configure"
> Result:
> error: CYGWIN_NT-10.0-x86_64 is not supported (yet?)
> 
> I have tried searching for this error (was really hard trying to go through the Cygwin web archives) and haven't seen it discussed.  I am pretty computer literate, but at this juncture I'm not sure how to proceed.  I've compiled a few programs before (from within Linux), have done some programming in the past, but am in no way "comfortable" or that knowledgeable about it and am officially stuck.
> 
> ANY responses would likely be appreciated.  Thank you in advance for any help/suggestions/clues!

BTDT, IIRC too many Linux dependencies.
Still running NTP from Meinberg:

https://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable
https://www.meinbergglobal.com/download/ntp/windows/ntp-4.2.8p15-v2-win32-setup.exe
https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm
https://www.meinbergglobal.com/download/ntp/windows/time-server-monitor/ntp-time-server-monitor-104.exe

You can download the sources and build the daemon and utilities with 
older VS releases, but Meinberg provides a service installer and monitor 
utility.

With serial driver and PPS DLL, service and other setup tweaking, you 
can run a serial GPS with PPS at Realtime priority and get microsecond 
stability.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  parent reply	other threads:[~2022-04-24 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 14:02 John Balkunas
2022-04-24 15:11 ` René Berber
2022-04-24 15:11   ` René Berber
2022-04-24 15:37   ` René Berber
2022-04-24 15:52     ` René Berber
2022-04-24 15:52       ` René Berber
2022-04-24 17:08 ` Brian Inglis [this message]
2022-04-24 18:47   ` John Balkunas

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=0ce7bb8a-af66-bf3c-e607-09cb20344271@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).