8.2.1 deb8 bindist fails to install on Windows 10 WSL

In principle the GHC 8.2.1 bindist for Debian 8 should work fine on WSL. However, in practice it fails during make install with this error,

"utils/ghc-cabal/dist-install/build/tmp/ghc-cabal-bindist" copy libraries/integer-gmp dist-install "strip" '' '/home/ben/roots/ghc/8.2.1' '/home/ben/roots/ghc/8.2.1/lib/ghc-8.2.1' '/home/ben/roots/ghc/8.2.1/share/doc/ghc-8.2.1/html/libraries' 'v p dyn'
./integer-gmp.cabal has been changed. Re-configuring with most recently used
options. If this fails, please run configure manually.
Configuring integer-gmp-1.0.1.0...
ghc-cabal: Cannot find the program 'ghc'. User-specified path
'/home/ben/bin-dist-8.2.1-Linux/ghc/inplace/bin/ghc-stage1' does not refer to
an executable and the program is not on the system path.
ghc.mk:986: recipe for target 'install_packages' failed
make[1]: *** [install_packages] Error 1
Makefile:51: recipe for target 'install' failed
make: *** [install] Error 2

changed milestone to %8.2.2

changed weight to 5

added Tbug Trac import labels

changed the description

It seems that the problem is that Cabal saves the path of the in-place ghc-stage1 from the build environment in libraries/integer-gmp/dist-install/setup-config. It's not clear why this only affects WSL.

CCing the usual Cabal-ers.

For comparison, the same bindist tarball (x86_64 deb8) for 8.0.2 installs just fine on WSL. Are you *sure* this works on other Ubuntu platforms on a virgin machine with no previous GHC install?

Due to #13304 (closed), this ticket isn't practical until either GHC HQ provides a bindist with

./configure --disable-large-address-space

or Microsoft fixes the WSL memory map bug.

Trac metadata

Trac field	Value
Related	- → #13304 (closed)

Indeed I suspect you are right; at this point I don't even think I own a machine that doesn't already have GHC installed. I'll try to setup a clean container and try installing there.

changed weight to 7

Bumping in priority as this likely affects all environments.

Trac metadata

Trac field	Value
Priority	normal → high

assigned to @bgamari

changed weight to 10

Trac metadata

Trac field	Value
Priority	high → highest

changed weight to 7

I'll admit I'm quite confused; I cannot reproduce this in a clean Debian 8 container. It seems that this really //is// WSL-only.

In light of this and the fact that GHC isn't really usable on WSL at the moment anyways, I'm going to demote this to high priority.

Trac metadata

Trac field	Value
Priority	highest → high

Tamar, you may be interested in this.

changed milestone to %8.2.3

It doesn't look like this is going to happen for 8.2.2.