Satish Balay <[email protected]> writes: > This issue is now fixed in cygwin dll [snapshot]. > > http://cygwin.com/ml/cygwin/2013-05/msg00342.html > http://cygwin.com/ml/cygwin/2013-05/msg00348.html
Does this mean we shouldn't bother with a work-around, or we should have configure test whether the bug exists and work around it only when necessary?
