Hi, as per summary: USE="profile" on haskeline requires USE="profile" on dev-haskell/mtl. Please adjust the dep to
--- errorsnippet ----
[26 of 26] Compiling System.Console.Haskeline.IO ( System/Console/Haskeline/IO.hs, dist/build/System/Console/Haskeline/IO.o )
Could not find module `Control.Monad.State':
Perhaps you haven't installed the profiling libraries for package `mtl-18.104.22.168'?
Use -v to see a list of the files searched for.
* ERROR: dev-haskell/haskeline-0.6.2.2 failed:
So this is not only one package.
Please crosscheck, there might be more that I did not spot!
USE="profile" on dev-haskell/haskeline requires
USE="profile" on dev-haskell/hashed-storage requires
There might be more, I'm still running some tests.
This affects almost all haskell packages, and huge amount of the dependencies.
As soon as a library "foo" depends on a library "bar" which allows USE="profile", the correct dependency would look like this;
That is, if package foo should be built with USE="profile", then package bar must have this flag too.
This is due to that you can't build profiled packages if not all your dependencies have been compiled with profiling too. But, it's ok that package bar has profiling and package foo hasn't.
So, in short, any package with CABAL_FEATURES="profile" must have [profile?] on the dependencies to all other packages that also allow CABAL_FEATURES="profile".
*** Bug 395187 has been marked as a duplicate of this bug. ***
*** Bug 399603 has been marked as a duplicate of this bug. ***
Out ebuild generating tool at last got support for it:
From now on newly coming ebuilds will contain (hopefully)
proper [profile?] style depends.
All newly generated packages get proper profile depends.
We will fix old ones on case-by-case basis.