From: "René Berber" <rene.berber@gmail.com>
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 10:11:38 -0500 [thread overview]
Message-ID: <9134ff4f-0ad3-1c53-63d8-df32fa6dc754@gmail.com> (raw)
Message-ID: <20220424151138.btsYxaf_p4NhuC8jVXKZMs9tIT1FYIGbi62Rel0ovOA@z> (raw)
In-Reply-To: <MN2PR11MB46950678BB5150B2CE71E8BCD2F99@MN2PR11MB4695.namprd11.prod.outlook.com>
On 4/24/2022 9:02 AM, John Balkunas wrote:
> 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:
[snip]
> Command: "./configure"
> Result:
> error: CYGWIN_NT-10.0-x86_64 is not supported (yet?)
That message is from chrony, there's no apparent problem with Cygwin.
The message is just telling you that the OS CYGWIN* is not one known to
work, or the project being already ported if that is needed.
Perhaps its time to look into configure's options, there may be one to
(force) build for Linux and, depending on how portable that project is,
it usually works.
Another detail which is often overlooked, you need to install the
pre-requisites (listed by the specific project) and its development
libraries (as in <package>-devel in setup).
Hope this helps.
--
R.Berber
next prev parent reply other threads:[~2022-04-24 15:11 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 [this message]
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
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=9134ff4f-0ad3-1c53-63d8-df32fa6dc754@gmail.com \
--to=rene.berber@gmail.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).