From: Tony Kelman <tony@kelman.net>
To: JonY <10walls@gmail.com>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-gcc-5.4.0-2 (x86/x86_64)
Date: Fri, 19 Aug 2016 19:06:00 -0000 [thread overview]
Message-ID: <DM2PR0201MB0799B8159F1557BE281B0971A7160@DM2PR0201MB0799.namprd02.prod.outlook.com> (raw)
In-Reply-To: <57B5C44B.4000108@gmail.com>
> The -2 build already includes the patch on the 66655 link.
Whoops, sorry I missed that, I accidentally downloaded the 5.4.0-1 src
package and build from that.
Another Julia developer also hit this and we're tracking it at
https://github.com/JuliaLang/julia/issues/18123 with a bit more
information.
Now that I got this to happen from an opensuse cross-compile this
looks like it's a GCC problem rather than specific to what version
cygwin has packaged, so I'll wait until we find out more. Will you
see any mingw-labeled bugs on the GCC tracker, or should we
specifically cc you?
> Yaakov,
>
> Can you restore 4.9.2-2 as previous? Thanks.
In the meantime it would be good to get 4.9.2-2 back as prev if
we can. Thanks!
-Tony
--
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
next prev parent reply other threads:[~2016-08-19 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 4:08 JonY
2016-08-16 9:20 ` Tony Kelman
2016-08-18 0:04 ` JonY
2016-08-18 9:35 ` Tony Kelman
2016-08-18 9:39 ` JonY
2016-08-18 11:51 ` Tony Kelman
2016-08-18 16:15 ` Tony Kelman
2016-08-18 16:37 ` JonY
2016-08-19 19:06 ` Tony Kelman [this message]
2016-08-20 2:29 ` JonY
2016-08-23 7:57 ` Tony Kelman
[not found] ` <DM2PR0201MB07999847654538389BC180BAA75E0@DM2PR0201MB0799.namprd02.prod.outlook.com>
2017-02-21 13:28 ` JonY
2017-02-21 14:45 ` Tony Kelman
2016-08-20 0:35 ` Yaakov Selkowitz
2016-08-20 1:52 ` JonY
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=DM2PR0201MB0799B8159F1557BE281B0971A7160@DM2PR0201MB0799.namprd02.prod.outlook.com \
--to=tony@kelman.net \
--cc=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).