Confirmed that installing llvm-3.4 and putting /usr/lib/llvm-3.4/bin first in PATH before running ghc lets it build working executables on armel and armhf.
This is certianly a bug in ghc. It should not depend on llvm, but on the llvm-$ver it was built against, and it should use the toolchain from that specific version of llvm. This could also be be considered a bug in llvm. Changing the dependency package to use llvm-3.5 less than a week before the slushy freeze is perhaps not the best idea? I think llvm should be prevented from migration to testing until this is sorted out in ghc and/or lvm, so I am leaving this bug assigned to both packages. There's also the worry of what happens if the autobuilders have built any haskell libraries using the new llvm on armel/hf. If there's been an ABI break in the code generated by llvm, that seems like it could get messy fast. -- see shy jo, off to work around this in order to get a security fix into testing
signature.asc
Description: Digital signature
