> Normally, new versions will first show up for cygwin native gcc before > being handed down to the cross compilers. I'll see about doing a test > version.
How long does building the cross-compiler from your cygport take, usually? I could try that and let you know if just applying the patch from https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/i386/winnt.c?r1=232828&r2=232827&pathrev=232828 would fix matters. Not sure how many other packaging changes you'd need to go from 5.4.0 to 6.1.0. (And 6.2 should be coming shortly.) According to the discussion in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655 the underlying issue may have also been a problem for cygwin targets, but I do much less testing there as Julia relies on async IO (via a fork of libuv) that cygwin doesn't provide. -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
