Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)

[Ryan Trinkle]

I would strongly urge that any new tarballs be released under new names,
and that the old tarballs be kept in place.  Changing existing tarball URLs
silently causes breakage for Nix, and, I would imagine, for any other build
systems that are particularly concerned with reproducibility.  Nix packages
based on GHC use an SHA-256 hash of the tarball to check it when
downloading, which of course will be broken by any change, no matter how
minor.

Of course, this doesn't necessarily impact the version number directly.

On Tue, Apr 4, 2017 at 8:15 AM, Phyx <lonetiger at gmail.com> wrote:

> We have discussed a few options on what to do, but haven't gotten a
> conclusion/concensus yet.
>
> Last we talked one option was presented to just re-tar the 7.10.3 and
> 8.0.2 tarballs with the fix. The gcc wrapper does not affect code
> generation of the compiler, it's just there to correct paths that are
> hard-coded in gcc because it was built to be used in MSYS2.
>
> 7.10.3 would be needed since we still support bootstrapping using it. This
> would be the easiest solution.
>
> Ben what do you think about changing the already released tarballs? Or
> would you prefer a full new release?
>
> On Tue, 4 Apr 2017, 09:18 Simon Peyton Jones via ghc-devs, <
> ghc-devs at haskell.org> wrote:
>
>> Yikes that sounds bad!
>>
>>
>>
>> I just wanted to raise awareness and offer myself to do guided grunt work
>> (if there is any) to push out a hotfix/inplace patch release for GHC 8.0.2.
>>
>>
>>
>> Help would be fantastic.   Phyx, Ben, etc: do we have a plan?
>>
>>
>>
>> Simon
>>
>>
>>
>> *From:* ghc-devs [mailto:ghc-devs-bounces at haskell.org] *On Behalf Of *Sebastian
>> Graf
>> *Sent:* 04 April 2017 09:12
>> *To:* ghc-devs <ghc-devs at haskell.org>
>> *Subject:* Windows 10 Creators Update will break GHC (Was FW: GHC on
>> Windows 10 15019+)
>>
>>
>>
>> Hi,
>>
>>
>>
>> when the Creators Update finally hits Windows 10 stable on April 11th
>> (next week), every currently available GHC will be broken by it.
>>
>>
>>
>> See [1] for the previous discussion, [2] and [3] for the tickets
>> discussing this. From what I read on the GHC 8.2 status wiki page, there
>> might be an interval of some weeks where it will not be possible to compile
>> a Haskell program on any up-to-date Windows 10 installation.
>>
>>
>>
>> I just wanted to raise awareness and offer myself to do guided grunt work
>> (if there is any) to push out a hotfix/inplace patch release for GHC 8.0.2.
>>
>>
>>
>> Greetings,
>>
>> Sebastian
>>
>>
>>
>> [1] http://haskell.1045720.n5.nabble.com/FW-GHC-on-Windows-
>> 10-15019-td5853491.html
>>
>> [2] https://ghc.haskell.org/trac/ghc/ticket/13411
>>
>> [3] https://ghc.haskell.org/trac/ghc/ticket/13472
>> _______________________________________________
>> ghc-devs mailing list
>> ghc-devs at haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20170404/1e6b592f/attachment.html>