dev-haskell/haddock-2.6.1 fails to build because of Ambiguous occurrence `display' in src/Haddock/GhcUtils.hs:53:37 Using strip found on system at: /usr/bin/strip Using tar found on system at: /bin/tar No uhc found Preprocessing library haddock-2.6.1... Preprocessing executables for haddock-2.6.1... Building haddock-2.6.1... [1 of 5] Compiling Haddock.GhcUtils ( src/Haddock/GhcUtils.hs, dist/build/Haddock/GhcUtils.o ) src/Haddock/GhcUtils.hs:53:37: Ambiguous occurrence `display' It could refer to either `Distribution.Text.display', imported from Distribution.Text at src/Haddock/GhcUtils.hs:27:0-23 or `Packages.display', imported from Packages at src/Haddock/GhcUtils.hs:32:0-14 * ERROR: dev-haskell/haddock-2.6.1 failed (compile phase): * setup build failed * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 3672: Called cabal_src_compile * environment, line 898: Called cabal-build * environment, line 754: Called die * The specific snippet of code: * ./setup build || die "setup build failed" Reproducible: Always Steps to Reproduce: emerge =dev-haskell/haddock-2.6.1
Created attachment 287061 [details] emerge --info =dev-haskell/haddock-2.6.1
Created attachment 287063 [details] emerge -pqv =dev-haskell/haddock-2.6.1
Created attachment 287065 [details] /var/tmp/portage/dev-haskell/haddock-2.6.1/temp/build.log
Created attachment 287067 [details] /var/tmp/portage/dev-haskell/haddock-2.6.1/temp/environment
Haddock is not of those packages which are easy to maintain across many Cabal versions. It's usually not too good idea to mix stable/unstable keywords for core haskell packages. So, you'll have to downgrade cabal down to Cabal-1.8 or migrate to ghc-.7 and mark all haskell stuff as ~arch.
(In reply to comment #5) > Haddock is not of those packages which are easy to maintain across many Cabal > versions. It's usually not too good idea to mix stable/unstable keywords for > core haskell packages. > > So, you'll have to downgrade cabal down to Cabal-1.8 or migrate to ghc-.7 and > mark all haskell stuff as ~arch. Thank you for your help. I have full understanding that it is hard to manage a stable/unstable mix. (Thank you for you work with gentoo and Haskell). I finally managed to fix it, I just wanted to file the bug to give some feedback of some of my build problems. I wish you a great day.
(In reply to comment #5) > Haddock is not of those packages which are easy to maintain across many > Cabal versions. It's usually not too good idea to mix stable/unstable > keywords for core haskell packages. > > So, you'll have to downgrade cabal down to Cabal-1.8 or migrate to ghc-.7 > and mark all haskell stuff as ~arch. This is happening to me all on amd64 (i.e., not ~amd64), on my first install of any Haskell stuff. I was trying to install dev-haskell/parsec-2.1.0.1 with USE=doc. - Using dev-lang/ghc-6.12.3, which I installed just a few minutes prior. - dev-haskell/cabal-1.10.2.0 was built without a hitch. - dev-haskell/haddock-2.6.1 failed out with the same errors. As a workaround, I added USE=-doc for dev-haskell/parsec, but I wanted to report that this isn't just affecting ~arch.
Pushed fix as: > 09 Mar 2012; Sergei Trofimovich <slyfox@gentoo.org> > +files/haddock-2.6.1-cabal-1.8.patch, haddock-2.6.1.ebuild: > Fix build failure against system's cabal-1.10 (use cabal bundled with ghc). > Fixes bug #383707 by Niklas Johansson and others. Thanks guys!
Thanks a lot!
