Cabal fails to right at the bootstrapping, in the line $(ghc-getghc) -i -i. -i"${WORKDIR}/${FP_P}" -cpp --make Setup.hs -o setup || die "compiling Setup.hs failed"; with the die message. Reproducible: Always Steps to Reproduce: Only »emerge -a1tv =dev-haskell/cabal-1.6.0.3«. Actual Results: ⋮ >>> Compiling source in /var/tmp/portage/dev-haskell/cabal-1.6.0.3/work/Cabal-1.6.0.3 ... * Bootstrapping Cabal... Language/Haskell/Extension.hs:50:7: Could not find module `Data.Array': Use -v to see a list of the files searched for. * * ERROR: dev-haskell/cabal-1.6.0.3 failed. ⋮ Expected Results: The installation of Cabal. Unfortunately, most packages either depend on cabal, or on a package that depends on cabal. Rendering the whole Haskell environment useless because »ghc-updater« can’t do its job anymore. Therefore I marked it as a blocker.
Hey, what's the reason for the priority lowering? Wasn't P2 the default priority for new bugs? I'm OK if it's not a blocker. But the priority change too? Is this some kind of weird “punishment”? I would have at least expected a explanation for the changes. You know, as usually.
Which GHC version did you use? $ ghc -V
(In reply to comment #2) $ ghc -V The Glorious Glasgow Haskell Compilation System, version 6.10.1 :D
(In reply to comment #2) Oh, and the USE flags are ghc: bash-completion doc -binary -ghcbootstrap -ghcmakebinary -ghcquickbuild cabal: doc -profile
Looks like you're using the overlay, yes? About bugs there, report them in #gentoo-haskell @ freenode or to our haskell@gentoo.org mail. Also, if you're using the ghc 6.10.x series, try the latest version, 6.10.4. Available both from the overlay and p.masked in portage. 6.10.1 from the overlay shouldn't be used. Cabal 1.6.0.3 is distributed with ghc-6.10.4 and shouldn't give you any trouble. ghc-updater has been replaced by haskell-updater, a separate package which has some new features.
(In reply to comment #5) > Looks like you're using the overlay, yes? Yes. I thought the [overlay-name] in the summary was the standard way of reporting bugs for overlays here. Sorry, if this was a misconception. > […] try the latest version, 6.10.4. > […] ghc-updater has been replaced by haskell-updater […] Hmm, they are both hard masked, so they hardly can be the recommended version to use. :) I’ll go ask in #gentoo-haskell.
(In reply to comment #5) > ghc-updater has been replaced by haskell-updater, a separate package which has > some new features. Ha, very funny. The installation of haskell-updater of course fails with “<command line>: unknown package: Cabal-1.6.0.3” . And now? ^^
I bet I know what the problem is... Navid installed cabal before we forgot to set CORE_LIB for it, and so if he upgraded Cabal then the one that GHC expects is missing... Can you provide the output of "ghc-pkg list | grep -i cabal" ?
(In reply to comment #8) Hey, thank you. :) The output is "{Cabal-1.6.0.1}, {Cabal-1.6.0.3}, {GLUT-2.1.1.2}, {HTTP-4000.0.5}," I just talked to someone of the #gentoo-haskell team, and he recommended installing ghc-6.10.4, because it goes with cabal-1.6.0.3. It is hard masked, but he told me that it's still the best solution. So I’m compiling ghc right now, and then will see, if cabal wants to install. If yes, everything is good. If not, I will try other options.
I don't think CABAL_CORE_LIB_GHC_PV has anything to do with this issue. cabal 1.6.0.1 was bundled with ghc 6.10.1, and cabal 1.6.0.3 with ghc 6.10.4. The error message is interesting though. Data.Array should be available in the array package, which is a build-depend in the cabal file. Your other error message puzzles me too, but I get no clue as there is no context. Anyway, good luck with your new installation ;)
(In reply to comment #10) > cabal 1.6.0.1 was bundled with ghc 6.10.1, and cabal 1.6.0.3 with ghc 6.10.4. Exactly. And I’m here to check back and report, that with ghc-6.10.4 cabal installed. But I had to use »USE="-doc" haskell-updater« in order to install things, until haddock was installed. So it was a bit messy, but in the end, it all worked out, even with the doc use flag enabled. > The error message is interesting though. Data.Array should be available in the > array package, which is a build-depend in the cabal file. I think it has to do with the array package existing, but for the wrong version of ghc. Or something like that. :) > Your other error message puzzles me too, but I get no clue as there is no > context. I could provide context if needed. I just would have to re-install the old ghc, and restore that buggy state first. I’d do it though, if it helped solve a big problem. > Anyway, good luck with your new installation ;) Thank you. As I said up there, it now works nicely. Only the encoding package’s well-known bug (extreme long compilation times and stack overflow when generating the documentation) remains. :) Thank you all for your work, people!
(In reply to comment #11) > (In reply to comment #10) > > cabal 1.6.0.1 was bundled with ghc 6.10.1, and cabal 1.6.0.3 with ghc 6.10.4. > Exactly. And I’m here to check back and report, that with ghc-6.10.4 cabal > installed. But I had to use »USE="-doc" haskell-updater« in order to install > things, until haddock was installed. So it was a bit messy, but in the end, it > all worked out, even with the doc use flag enabled. Ok, we'll look into USE=doc haskell-updater and see what we can do about it. > > Your other error message puzzles me too, but I get no clue as there is no > > context. > I could provide context if needed. I just would have to re-install the old ghc, > and restore that buggy state first. I’d do it though, if it helped solve a > big problem. Never mind. If it happens with your new environment we're more interested. > > Anyway, good luck with your new installation ;) > Thank you. As I said up there, it now works nicely. Only the encoding > package’s well-known bug (extreme long compilation times and stack overflow > when generating the documentation) remains. :) > > Thank you all for your work, people! np, glad you enjoy it ;)
Hmmm... which version of haddock do you have? the only possible problems I can think of is that either you're somehow using a version of haddock which still deps on ghc-paths, or else it's somehow trying to build docs for cabal...
(In reply to comment #13) I consider the bug solved. But for your information: I used to use haddock 2.4.1, but had to unmask 2.4.2 now, to get it all working.
