From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)
Date: Wed, 18 Oct 2017 07:30:00 -0000 [thread overview]
Message-ID: <9b4ea17e-1388-6f32-0419-c7ecc29bbf59@gmail.com> (raw)
In-Reply-To: <59e5edce.8237ca0a.705b2.909e@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 637 bytes --]
On 10/17/2017 11:47 AM, Steven Penny wrote:
> On Sun, 20 Aug 2017 14:16:07, JonY wrote:
>> The mingw-w64 cross compilers have been updated:
>>
>> * mingw64-i686-binutils-2.28.1.12c1f20d
>> * mingw64-i686-gcc-6.3.0-1
>> * mingw64-x86_64-binutils-2.28.1.12c1f20d
>> * mingw64-x86_64-gcc-6.3.0-1
>
> http://cygwin.com/ml/cygwin/2017-08/msg00182.html
>
> Can mingw64-{x86_64,i686}-gcc move to Current? These were released about 2
> months ago, and it seems the only issue was with binutils, which has
> already
> been fixed and moved to current. Please and thank you.
>
Sure, I'll bump it soon, thanks for testing.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
prev parent reply other threads:[~2017-10-18 7:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 16:19 JonY
2017-08-21 1:57 ` Steven Penny
2017-08-21 2:45 ` Steven Penny
2017-08-22 2:22 ` Steven Penny
2017-08-22 12:47 ` JonY
2017-09-19 23:14 ` Steven Penny
2017-09-21 0:10 ` Steven Penny
2017-09-24 0:49 ` JonY
2017-09-24 3:07 ` Steven Penny
2017-09-25 1:53 ` Steven Penny
2017-09-25 14:18 ` JonY
2017-09-25 18:33 ` Steven Penny
2017-09-27 23:43 ` JonY
2017-09-28 4:13 ` Steven Penny
2017-09-25 16:43 ` Hans-Bernhard Bröker
2017-09-25 18:44 ` Steven Penny
2017-09-25 20:04 ` Hans-Bernhard Bröker
2017-09-27 4:35 ` Andrey Repin
2017-10-17 11:47 ` Steven Penny
2017-10-18 7:30 ` JonY [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=9b4ea17e-1388-6f32-0419-c7ecc29bbf59@gmail.com \
--to=10walls@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).