ghc-6.6 and previous have ppc and ppc64 as keywords, but not ghc-6.6.1. Did not notice as I was using the haskell overlay which does include those keywords. Reproducible: Always
(In reply to comment #0) > ghc-6.6 and previous have ppc and ppc64 as keywords, but not ghc-6.6.1. Did > not notice as I was using the haskell overlay which does include those > keywords. We've been getting reports that it does not work at all with recent gcc versions. What gcc version are you using? 4.1.x or 4.2.x ? If it's working for you perhaps you can provide us with a binary so we can provide that in the standard portage ebuild. See: http://haskell.org/~gentoo/gentoo-haskell/projects/build-ghc-bin.sh and talk to us about it on #gentoo-haskell
I believe this version was built with gcc-4.1.2. Seems to work fine, I can certainly provide a package. How do I check the compiler version ghc was built with? Current system uses gcc-4.2.2 with glibc-2.6.1.
(In reply to comment #2) > I believe this version was built with gcc-4.1.2. Seems to work fine, I can > certainly provide a package. > How do I check the compiler version ghc was built with? I'm not sure we can easily. > Current system uses gcc-4.2.2 with glibc-2.6.1. Ah, we're pretty sure ghc has issues with gcc-4.2 though it ought to work with 4.1 as you say. We do have a fix for building ghc-6.6 with gcc-4.2 on x86, we should apply that and see if it helps ppc.
I'll make a package of the current ghc version and try to rebuild with 4.2.2.
Fails with 4.2.2, now trying with 4.1.2 with glibc-2.6.1
(In reply to comment #5) > Fails with 4.2.2, now trying with 4.1.2 with glibc-2.6.1 > -fno-toplevel-reorder, fixed suggested on hackage for gcc-4.2.x, either does not work on ppc or I am not applying it correctly. Added to make.conf to test.
(In reply to comment #6) > -fno-toplevel-reorder, fixed suggested on hackage for gcc-4.2.x, either does > not work on ppc or I am not applying it correctly. Added to make.conf to test. Unfortunately it cannot be used that easily since it has to *replace* the -fno-unit-at-a-time flag that ghc passes to gcc. So that requires a patch to ghc's gcc driver code.
ghc-6.6.1 includes a ppc binary (well, a -O2 build on a G4, nothing very fancy, as it has to work across all of ppc). What needs to be done now?
(In reply to comment #8) > ghc-6.6.1 includes a ppc binary (well, a -O2 build on a G4, nothing very fancy, > as it has to work across all of ppc). Fantastic. Thanks very much. > What needs to be done now? I guess we're done really or have I forgotten something? The ppc team are welcome to mark 6.6.1 stable whenever they see fit. If you want more work to do, there's always ppc64 for ghc 6.6.1. :-) At some point we'll come asking for help with ghc-6.8.2. :-)
I have been trying to build ghc-6.8.1 on ppc. There were a number of issues with cruft from 6.6.1. Once those were resolved ghc-6.8.1 was able to build ghc-6.8.1 using gcc-4.2.2. I think that was because I had cleaned out the cruft and uninstalled all haskell packages except for a binary of ghc-6.8.1 that was built with gcc-4.1.2. There was an issue with haddock-0.8 which was resolved by copying over the darcs haddock files and recreating the haddock tar file. Cabal-1.2.2.0 needs to be used as other versions didn't build. Haven't rebuilt the other haskell packages using the ghc compiled with gcc-4.2.2.
ghc-6.6.1 has been in the tree for ~ppc for over a month. Perhaps we should think about getting it marked stable. It's stable on the other major arches. We're nearly ready to put ghc-6.8.2 into portage, at least for amd64 and x86. We'll need some help with ppc. Most packages work with 6.8 now so there should be less problems. We'll be putting the updated libs into portage soon.
Closing since dev-lang/ghc-6.6.1 is stable on ppc and 6.8.2 is ~ppc.
