The gtk2hs ebuild is looking for the mtl (Monad Transformer Library). This has apparently been rolled into ghc so if that Haskell compiler is in use the requirement should be removed. I have tried forcing the install of mtl but the ebuild just says that it doesn't do anything and has been included with ghc-6.6.1. If you don't force it you get a block message when trying to install with 6.6.1. Reproducible: Always Steps to Reproduce: 1. Install ghc-6.6.1 2. try to install gtk2hs 3. Actual Results: failure of configure script on failure to find deprecated mtl library. Expected Results: installed gtk2hs
Created attachment 136558 [details] ebuild log file
> !!! Please attach the following file when filing a report to bugs.gentoo.org: > !!! /var/tmp/portage/dev-haskell/gtk2hs-0.9.12.1/work/gtk2hs-0.9.12.1/config.log Please do it...
Created attachment 136566 [details] gtk2hs config.log
I posted the requested info. I should also note that I've compiled both ghc-6.6.1 and gtk2hs from tarballs and did not see this problem in the configure phase.
Hmm that's odd. What does ghc-pkg list mtl report?
(In reply to comment #5) > Hmm that's odd. What does ghc-pkg list mtl report? > /home/greg/workshop/ghc-install/lib/ghc-6.6.1/package.conf: mtl-1.0.1 /home/greg/.ghc/x86_64-linux-6.6.1/package.conf:
(In reply to comment #6) > (In reply to comment #5) > > Hmm that's odd. What does ghc-pkg list mtl report? > > > > /home/greg/workshop/ghc-install/lib/ghc-6.6.1/package.conf: > mtl-1.0.1 > /home/greg/.ghc/x86_64-linux-6.6.1/package.conf: > That's from my private installation compiled from source. I already downgraded to ghc-6.4.2 in the portage system. I can reinstall but it takes a long time to compile.
> > /home/greg/workshop/ghc-install/lib/ghc-6.6.1/package.conf: > > mtl-1.0.1 > That's from my private installation compiled from source. Ah, ok so that's a completely different ghc installation. > I already downgraded to ghc-6.4.2 in the portage system. So gtk2hs-0.9.12.1 does depend on dev-haskell/mtl. The most common way this ends up not working is if one upgrades from an older ghc and does not run ghc-updater, so portage still thinks dev-haskell/mtl is installed, but ghc-pkg doesn't know about it as it was compiled for an older ghc version. So my best guess for what was happening is that mtl simply was not installed for ghc-6.6.1. It was probably installed for an older ghc and portage simply doesn't know that's not good enough. That's what we use ghc-updater for. > I can reinstall but it takes a long time to compile. You can USE=binary emerge ghc and then it's pretty quick. So if you upgrade to ghc-6.6.1 again via portage, then before installing gtk2hs again, make sure that the portage ghc knows about mtl. You may find you've still got an mtl package installed but for an older ghc. If that's the case, then either unmerge mtl or re-emerge it or run ghc-updater. Then when you emerge gtk2hs it'll pull in mtl. Let us know how you get on.
(In reply to comment #8) > > > /home/greg/workshop/ghc-install/lib/ghc-6.6.1/package.conf: > > > mtl-1.0.1 > > > That's from my private installation compiled from source. > > Ah, ok so that's a completely different ghc installation. > Yeah, I just provided that to show that you *can* install gtk2hs with 6.6.1 without trouble if you build from source. I've installed the 6.6.1 binary and run ghc-updater. I think I figured out the problem. I am using ~amd64 to get the new version of gtk2hs but was not using it for mtl. I now added that in package.keywords and it seems that at least the versions are right. Before gtk2hs was requiring mtl-1.0 and that in turn was requiring a downgrade of ghc to 6.4.2. When I installed from source I installed the extralibs package which contains mtl as well. You guys must have that stuff as separate ebuilds whereas it gets built along with ghc if you have the extralibs package installed on top of the compiler tree. That's why I thought it was part of ghc. OK, I ran the emerge and it got through the mtl trouble spot. It's now compiling. It takes about 2 hours to finish on this machine so I'll assume the problem is fixed. Thanks for all your help.
