Phyx and friends: does this ring a bell? Do we have a ticket?
-Original Message-
From: Glasgow-haskell-users [mailto:glasgow-haskell-users-boun...@haskell.org]
On Behalf Of J. Garrett Morris
Sent: 09 March 2017 17:54
To: GHC users
Subject: GHC on Windows 10 15019+
Hi y'all,
I've recen
Hi Simon,
No it doesn't ring a bell to me, though I don't generally use the insider
builds. I think 0xc142 is a compatibility error, but what is not clear
to me is if he replaced realgcc which is a stub we make or just updated
things in the mingw folder. So I can't really tell if the error is
://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@haskell.org
http://mail.haskell.org/cgi-bin
se 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
>
] On Behalf Of Sebastian Graf
Sent: 04 April 2017 09:12
To: ghc-devs
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
>
> Help would be fantastic. Phyx, Ben, etc: do we have a plan?
>
>
>
> Simon
>
>
>
> *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of
> *Sebastian
> Graf
> *Sent:* 04 April 2017 09:12
> *To:* ghc-devs
> *Subject:* Wind
s 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-boun...@haskell.org
Phyx writes:
> We have discussed a few options on what to do, but haven't gotten a
> conclusion/concensus yet.
>
Tamar and I have discussed this on IRC in the passed. I tend to agree
that we will need to, at the very least, put out a new 8.0.2. I'm not
sure about 7.10. Moreover, there is reported
Ryan Trinkle writes:
> 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 wit
