Re: GHC 8.2.1-rc1 source tarball availability
I don't know how to produce a binary distribution but I did do a build on Mac OS 10.12.4 with XCode 8.3. It went flawlessly and subjectively seemed much faster than previous builds. I then did a cabal install of hlint and verified that hlint worked. On Tue, Apr 4, 2017 at 1:22 AM Ben Gamariwrote: > > tl;dr: If you would like to produce a binary distribution for GHC >8.2.1-rc1 then let me know, grab the source distribution and >start building. The binary distributions will be announced one >week from today. > > Hello GHC packagers, > > I am happy to announce the release of the 8.2.1-rc1 source distribution > to binary packagers. You will find the usual source artifacts at > > http://downloads.haskell.org/~ghc/8.2.1-rc1/ > > As usual, the sooner we can get the binary distributions together the > better, but I will hold off on announcing the distributions until next > Sunday to ensure we're all on the same page. It would be appreciated if > you could reply to this message confirming that you intend to offer a > binary distribution this release. > > Otherwise, let me know if you have any trouble building your > distribution. I have yet to push the ghc-8.2.1-rc1 tag in case we > encounter unexpected issues but all of my builds with this tarball > thusfar have gone swimmingly save a few known issues (namely #13426, > #13233, and #13509). > > Good luck and thanks for all of your work! > > Cheers, > > - Ben > > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)
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@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-boun...@haskell.org] *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. > > > > 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@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)
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, Phyxwrote: > 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@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-boun...@haskell.org] *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. >> >> >> >> 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@haskell.org >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >> > > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: GHC 8.2.1-rc1 source tarball availability
Alan & Kim Zimmermanwrites: > There is no tag in the source tree, which commit has been used? > As I mention in the message, I intentionally held off on pushing the tag to avoid the need to force push in case this commit ends up being bad. The tarball was produced from d67f0471cd3584c5a548ff30c9023b599b598d3e. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)
Phyxwrites: > 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 reportedly a non-negligible fraction of users still using 7.8 releases, although I'm not keen on going back that far given that this was pre-submodules. > 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? > We certainly can't change the existing tarballs. However, we could just push out a 7.10.4 (or perhaps 7.10.3b, I'm unsure) release with binary distributions for Windows only. There are a few unrelated patches on the ghc-7.10 branch that weren't present in 7.10.3, but I believe they are quite low-risk. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)
Ryan Trinklewrites: > 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. > I completely agree here; I avoid updating existing artifacts whenever possible. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
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@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: GHC 8.2.1-rc1 source tarball availability
$ tar xOf ghc-8.2.0.20170404-src.tar.xz ghc-8.2.0.20170404/GIT_COMMIT_ID ; echo d67f0471cd3584c5a548ff30c9023b599b598d3e On Tue, Apr 4, 2017 at 9:01 AM Alan & Kim Zimmermanwrote: > There is no tag in the source tree, which commit has been used? > > Alan > > On 4 April 2017 at 06:21, Ben Gamari wrote: > > > tl;dr: If you would like to produce a binary distribution for GHC >8.2.1-rc1 then let me know, grab the source distribution and >start building. The binary distributions will be announced one >week from today. > > Hello GHC packagers, > > I am happy to announce the release of the 8.2.1-rc1 source distribution > to binary packagers. You will find the usual source artifacts at > > http://downloads.haskell.org/~ghc/8.2.1-rc1/ > > As usual, the sooner we can get the binary distributions together the > better, but I will hold off on announcing the distributions until next > Sunday to ensure we're all on the same page. It would be appreciated if > you could reply to this message confirming that you intend to offer a > binary distribution this release. > > Otherwise, let me know if you have any trouble building your > distribution. I have yet to push the ghc-8.2.1-rc1 tag in case we > encounter unexpected issues but all of my builds with this tarball > thusfar have gone swimmingly save a few known issues (namely #13426, > #13233, and #13509). > > Good luck and thanks for all of your work! > > Cheers, > > - Ben > > > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: GHC 8.2.1-rc1 source tarball availability
There is no tag in the source tree, which commit has been used? Alan On 4 April 2017 at 06:21, Ben Gamariwrote: > > tl;dr: If you would like to produce a binary distribution for GHC >8.2.1-rc1 then let me know, grab the source distribution and >start building. The binary distributions will be announced one >week from today. > > Hello GHC packagers, > > I am happy to announce the release of the 8.2.1-rc1 source distribution > to binary packagers. You will find the usual source artifacts at > > http://downloads.haskell.org/~ghc/8.2.1-rc1/ > > As usual, the sooner we can get the binary distributions together the > better, but I will hold off on announcing the distributions until next > Sunday to ensure we're all on the same page. It would be appreciated if > you could reply to this message confirming that you intend to offer a > binary distribution this release. > > Otherwise, let me know if you have any trouble building your > distribution. I have yet to push the ghc-8.2.1-rc1 tag in case we > encounter unexpected issues but all of my builds with this tarball > thusfar have gone swimmingly save a few known issues (namely #13426, > #13233, and #13509). > > Good luck and thanks for all of your work! > > Cheers, > > - Ben > > > ___ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)
Also note that a minimal patch already exists which will ship in GHC 8.2: https://git.haskell.org/ghc.git/commitdiff/018ac7f4b2f7345e28d21fb1f99b44dbc79f6e85 It's 'just' a matter of packaging that up in a hotfix. On Tue, Apr 4, 2017 at 10:12 AM, Sebastian Grafwrote: > 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@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
RE: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)
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-boun...@haskell.org] On Behalf Of Sebastian Graf Sent: 04 April 2017 09:12 To: ghc-devsSubject: 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@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs