Bug#787227: Acknowledgement (broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No s

Note that this bug is likely a security hole; /usr/bin/ghc loading .so files relative to the CWD could be exploted. When ghc's postinst runs ghc-pkg, it seems that dpkg does something that prevents those relative paths being used (possibly just a chdir, didn't check). So, it's at least not

Bug#787227: Acknowledgement (broken on armel due to broken RUNPATH: /usr/lib/ghc/bin/ghc: error while loading shared libraries: libHShaskeline-0.7.1.2-ghc7.8.4.so: cannot open shared object file: No s

FWIW, I have seen this on 2 machins: * Bannana pi, running bannanian with a Debian armel chroot * Cubietruck, running an image from https://romanrm.net/a10/debian with a Debian armel chroot In both cases, the kernel and boot system are armhf. I don't know if this nonstandard configuration has