Re-adding ghc-devs. | Settup up things so that all master pushes go through a build&smoke-test-on- | all-relevant-platforms purgatory shouldn't be that problematic.. I know. We discuss it periodically The trouble is that it takes work to do these things (reliably, solidly) and everyone is busy. If someone felt able to step up to doing it, it'd be great. Simon | -----Original Message----- | From: Kosyrev Serge [mailto:skosyrev@ptsecurity.com] | Sent: 22 February 2017 14:18 | To: Simon Peyton Jones | Subject: Re: Windows build broken | | Simon, | | It pains me to see how something trivially preventable by a functioning | "continuous integration" setup keeps causing you trouble so regularly. | | Settup up things so that all master pushes go through a build&smoke-test-on- | all-relevant-platforms purgatory shouldn't be that problematic.. | | I know, it's not my ground to meddle in, but I just can't be calmly watching | this entirely preventable suffering.. | | Simon Peyton Jones via ghc-devs writes: | > Please please please could some one fix this? On windows. | > | > It’s frustrating being unable to build. | > | > Please | > | > please | > | > Simon | > | > libraries\time\lib\Data\Time\Clock\Internal\SystemTime.hs:57:5: error: | > | > Not in scope: data constructor FILETIME | > | > Perhaps you meant Win32.FILETIME (imported from System.Win32.Time) | > | > | | > | > 57 | FILETIME ft <- Win32.getSystemTimeAsFileTime | > | > | ^^^^^^^^ | | -- | с уважениeм / respectfully, not a GHC developer at all, Косырев Сергей | -- | “Most deadly errors arise from obsolete assumptions.” | -- Frank Herbert, Children of Dune