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

[Edmund Grimley Evans]

> Can you please try with the latest version of GHC available in unstable (9.4.7-1)?

I think the problem still exists:

$ wget http://ftp.debian.org/debian/pool/main/g/ghc/ghc_9.4.7-1_armhf.deb
$ ar pf ghc_9.4.7-1_armhf.deb data.tar.xz | tar xJf -
$ file usr/lib/ghc/bin/ghc-9.4.7
usr/lib/ghc/bin/ghc-9.4.7: ELF 32-bit LSB executable, ARM, EABI5
version 1 (SYSV), dynamically linked, interpreter
/lib/ld-linux-armhf.so.3, for GNU/Linux 3.2.0,
BuildID[sha1]=363ee1eef5ed7a7df5782524eb2734e366865c9c, stripped
$ readelf -l usr/lib/ghc/bin/ghc-9.4.7 | grep LOAD
  LOAD           0x000000 0x00008000 0x00008000 0x1f767c 0x1f767c R E 0x1000
  LOAD           0x1f7df8 0x00200df8 0x00200df8 0x12ea8 0x12ea9 RW  0x1000

So the binary is non-PIE and loads at 0x8000 but many systems have
mmap_min_addr set to 0x10000 (I believe).

But perhaps it's not such a serious problem. It looks like people can change
the value if they need to: https://wiki.debian.org/mmap_min_addr

So I won't object if you want to close this ancient bug.