https://bugzilla.redhat.com/show_bug.cgi?id=1195231
Jens Petersen petersen@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #5 from Jens Petersen petersen@redhat.com --- The current suspicion is that the problem is related to ghc dynlinking on aarch64: the statically linked ghc binaries don't exhibit the problem.
I managed to build ghc-7.10.1 RC3 on F21 aarch64 using DYNAMIC_GHC_PROGRAMS=NO.
Next I plan to backport the needed patches to 7.8.4 and build it too with DYNAMIC_GHC_PROGRAMS=NO on aarch64. Until the root (linking?) problem is fixed that seems the best short-term solution currently. It is unclear at the moment if all executables will need to be Haskell statically linked to work properly.
GHC upstream will not support aarch64 officially 7.12 and will use llvm like the 32bit arm port. It will require llvm-3.6 which should include the needed ghc calling conventions. So F23 (assuming we move to 7.10) will likely be in a similar position to F22 but at least we know it builds with gcc there already. :)