Cabal folk: it looks as if updating Cabal has made GHC on Windows break. Might you investigate?
See below Thanks Simon -----Original Message----- From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Páli Gábor János Sent: 09 October 2014 06:15 To: ghc-d...@haskell.org Subject: Re: Building ghc on Windows with msys2 2014-10-07 17:02 GMT+02:00 Páli Gábor János <pali.ga...@gmail.com>: > 2014-10-07 15:04 GMT+02:00 cg <chengan...@gmail.com>: >> I guess the current two build server are all Cygwin based, they are >> failing at the same permission issue at early building stage, it >> prevents checking out the real problem. It seems msys2 (or msys) >> seldom has such issue. > > For what it is worth, I have been witnessing those permission issues > with msys2 on my Windows builders. They worked (more or the less) > fine until September 24, but suddenly, something has changed (not on > my side) and all I got those errors since. Looks like the commit with the Cabal submodule update causes this [1]. The revision before that commit still builds fine on my system, while everything else after that commit dies early at build [2]. Is this only me, has anybody else experienced the problem? Perhaps I am doing something wrong? I do not remember to see any related "heads-up" message on the list, like I should update any of the build-time dependencies. [1] http://git.haskell.org/ghc.git/commit/4b648be19c75e6c6a8e6f9f93fa12c7a4176f0ae [2] http://haskell.inf.elte.hu/builders/windows-x86-head/56/10.html _______________________________________________ ghc-devs mailing list ghc-d...@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs _______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
