From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Update mingw-w64 headers
Date: Tue, 29 Oct 2019 05:00:00 -0000 [thread overview]
Message-ID: <c6cbb16e-9b2c-320e-aaa8-5f69bc6ea6af@SystematicSw.ab.ca> (raw)
In-Reply-To: <CALK-3mKT=HLf2-_En+jv2twgEVq8Az+RZRTEYu0JuKf+-RPhSg@mail.gmail.com>
On 2019-10-28 22:48, Biswapriyo Nath wrote:
> I did not mean the release page [1]. I mean the cygwin headers is older
> than the current mingw-w64 git repository [2]. The latest tag is v6.0.0.
> [3]
>
> Wait, did you mean there should be a new "stable" tag or release in
> mingw-w64 so that cygwin can import it?
>
> [1]: http://mingw-w64.org/doku.php/download
> [2]: https://sourceforge.net/p/mingw-w64/mingw-w64/ci/master/tree/
> [3]: https://sourceforge.net/p/mingw-w64/mingw-w64/ref/master/tags/
Did you read what I posted or check the content at the links?
Mingw64 release is 6.0.0 and so are Cygwin packages mingw64-*86-headers!
Mingw64 6 was released at the end of last year and Cygwin packages were updated
to 6 at the start of this year.
Where is the discrepancy between Mingw64 and Cygwin headers?
The Mingw64 master/HEAD/tip may not be identical to current Cygwin, as Cygwin
tracks stable package release sources, but will sometimes cherry pick CVE fixes
to patch between releases.
--
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.
--
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
prev parent reply other threads:[~2019-10-29 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 17:20 Biswapriyo Nath
2019-10-29 0:22 ` Brian Inglis
2019-10-29 4:49 ` Biswapriyo Nath
2019-10-29 5:00 ` Brian Inglis [this message]
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=c6cbb16e-9b2c-320e-aaa8-5f69bc6ea6af@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).