2014-10-26 18:17 GMT+01:00 Gintautas Miliauskas
Maybe it's something silly like one process not having enough time to clean up and close the file before the next command tries to move it? I'd add a sleep before the mv and see if that helps.
I am far from understanding all the details of the problem, but I believe the move operation originates from the ghc-cabal binary. For what it is worth, I could not even find the place in the sources where the referenced MoveFileEx is called: "inplace/bin/ghc-cabal.exe" configure libraries/binary dist-boot "" --with-ghc="/ghc-7.6.3/bin/ghc.exe" --with-ghc-pkg="/ghc-7.6.3/bin/ghc-pkg" --package-db=C:/msys32/home/ghc-builder/work/builder/tempbuild/build/libraries/bootstrapping.conf --disable-library-for-ghci --enable-library-vanilla --enable-library-for-ghci --disable-library-profiling --disable-shared --with-hscolour="/c/Users/ghc-builder/AppData/Roaming/cabal/bin/HsColour" --configure-option=CFLAGS=" -U__i686 -march=i686 -fno-stack-protector " --configure-option=LDFLAGS=" " --configure-option=CPPFLAGS=" " --gcc-options=" -U__i686 -march=i686 -fno-stack-protector " --constraint "binary == 0.7.1.0" --constraint "Cabal == 1.21.1.0" --constraint "hpc == 0.6.0.2" --constraint "bin-package-db == 0.0.0.0" --constraint "hoopl == 3.10.0.2" --constraint "transformers == 0.4.1.0" --with-gcc="C:/msys32/ghc-7.6.3/lib/../mingw/bin/gcc.exe" --configure-option=--with-cc="C:/msys32/ghc-7.6.3/lib/../mingw/bin/gcc.exe" --with-ar="C:/msys32/ghc-7.6.3/lib/../mingw/bin/ar.exe" --with-alex="/c/Users/ghc-builder/AppData/Roaming/cabal/bin/alex" --with-happy="/c/Users/ghc-builder/AppData/Roaming/cabal/bin/happy" Configuring binary-0.7.1.0... ghc-cabal.exe: dist-boot\setup-config3736.tmp: MoveFileEx "dist-boot\\setup-config3736.tmp" "dist-boot\\setup-config": permission denied (Access is denied.) libraries/binary/ghc.mk:3: recipe for target 'libraries/binary/dist-boot/package-data.mk' failed
Does the build proceed if you try "make" without cleaning the repository, or does it hang again at the same spot?
It is fully reproducible by the subsequent make(1) invocations as
well, that is, yes, it hangs at the same spot.
2014-10-28 17:18 GMT+01:00 Gintautas Miliauskas
Any luck with getting the Windows continuous builds back up and running?
No, not yet. But I will keep posted on the results.
I'd be willing to try to help out if remote access is available
I think this could be arranged.
although the build environment should be updated first in case that's the source of the trouble.
Right, I will contact you off-list about this once I moved to toolchain versions to the ones recommended at the Windows build page.