Bug#864846: ghc: on armhf should have load address of at least 0x10000

[Edmund Grimley Evans]

Source: ghc
Version: 8.0.1-17+b1

If I try to run "ghc" in one of my armhf chroots, it does not work very well:

$ ghc
Segmentation fault

$ wget http://ftp.debian.org/debian/pool/main/g/ghc/ghc_8.0.1-17+b1_armhf.deb
$ ar pf ghc_8.0.1-17+b1_armhf.deb data.tar.xz | tar xJf -
$ readelf -l usr/lib/ghc/bin/ghc | grep LOAD
  LOAD           0x000000 0x00008000 0x00008000 0x19bc74 0x19bc74 R E 0x1000
  LOAD           0x19beb0 0x001a4eb0 0x001a4eb0 0x21d8c 0x21d8d RW  0x1000

Probably this binary should be a PIE, like nearly all other
executables in the system. Failing that, it should have a load address
of 0x10000 instead of 0x8000 because many kernels are configured not
to allow an mmap below 0x10000.

I presume this problem concerns all binaries generated by GHC.

However, I hope it does not prevent any armhf binary from running
under a Debian armhf stock kernel image.