GHC 7.6.2

[aristidb]

It compiles fine, parallel build active, on my x86_64 NixOS machine.

[aristidb]

Also successfully builds on OS X 10.7.

[peti]

In my experience, parallel build errors occur because the makefile underspecifies (or mis-states) the dependencies. If that is the case, then those issues will usually arise regardless of whether make is being run on Linux, Darwin, or any other system. I also don't see any system-specific stuff in the error messages shown below. So I wonder ... what makes you believe that race conditionts in the build system might dependent on the system platform?

[aristidb]

Nothing other than build errors often being architecture specific. My hope
is that 7.6.2 fixed these errors either way.
Am 30.01.2013 11:26 schrieb "Peter Simons" notifications@github.com:

In pkgs/development/compilers/ghc/7.6.2.nix:

+stdenv.mkDerivation rec {

• version = "7.6.2";

• name = "ghc-${version}";

• src = fetchurl {
• url = "http://haskell.org/ghc/dist/${version}/${name}-src.tar.bz2";
• sha256 = "d5f45184abeacf7e9c6b4f63c7101a5c1d7b4fe9007901159e2287ecf38de533";
• };

• buildInputs = [ ghc perl gmp ncurses ];

• The comments below applied to GHC 7.6.1, left for if somebody experiences

• similar problems. If so, I argue we should selectively disable parallel

• building JUST for that platform. ~aristidb

In my experience, parallel build errors occur because the makefile
underspecifies (or mis-states) the dependencies. If that is the case, then
those issues will usually arise regardless of whether make is being run
on Linux, Darwin, or any other system. I also don't see any system-specific
stuff in the error messages shown below. So I wonder ... what makes you
believe that race conditionts in the build system might dependent on the
system platform?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/291/files#r2824096.

[peti]

Yes, I too hope that 7.6.2 compiles fine with parallel building enabled.

If it does not, however, then we should probably not assume that this issue might be platform-specific. There seems to be no evidence to support that assumption.