From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request update GCC
Date: Sun, 13 Aug 2017 04:19:00 -0000 [thread overview]
Message-ID: <82c60d28-a440-4450-ad8a-d84f628740f5@gmail.com> (raw)
In-Reply-To: <598bb28d.8549ca0a.c6ebc.b044@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]
On 08/10/2017 01:10 AM, Steven Penny wrote:
> On Sat, 24 Jun 2017 19:21:57, Steven Penny wrote:
>> gcc-core, gcc-g++
>> ==================
>> - version: 5.4.0-1
>> - version: 6.3.0-1 [test]
>> - Jonathan Yong (JonY)
>>
>> mingw64-x86_64-gcc-core, mingw64-x86_64-gcc-g++
>> ===============================================
>> - version: 5.4.0-3
>> - Jonathan Yong (JonY)
>>
>> mingw64-i686-gcc-core, mingw64-i686-gcc-g++
>> ===========================================
>> - version: 5.4.0-4
>> - Jonathan Yong (JonY)
>
> http://cygwin.com/ml/cygwin/2017-06/msg00310.html
>
> Now that the issue with readline has been resolved, thanks to great work by
> Corinna and Eric, I wanted to revist some other of my issues. I am
> reposting
> this because it is a new month.
>
> Some work was done on this in June and July, but I still do not see even
> a test
> version with the mingw64-*-gcc-* packages. I use Cygwin quite a bit, but
> when I
> can I prefer to build Windows native versions of programs, this way I
> can share
> them without worrying about the Cygwin DLL.
>
> Can we please release at least test versions of the mingw64-*-gcc-*
> packages?
>
Sure, I'll start bringing up mingw-w64 6.x within the week.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
prev parent reply other threads:[~2017-08-13 4:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 2:22 Steven Penny
2017-06-25 4:03 ` JonY
2017-06-26 1:11 ` JonY
2017-06-26 19:27 ` Christian Franke
2017-06-28 23:14 ` JonY
2017-06-26 10:16 ` Marco Atzeri
2017-06-27 1:09 ` JonY
2017-06-27 11:33 ` Marco Atzeri
2017-06-28 2:22 ` Ken Brown
2017-06-28 11:34 ` Marco Atzeri
2017-08-10 1:10 ` Steven Penny
2017-08-13 4:19 ` 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=82c60d28-a440-4450-ad8a-d84f628740f5@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).