based on "ghc-pkg list" ....
in my "global" ghc install I have bytestring-0.9.0.1
in my "local" ghc install I have bytestring-0.9.1.0
this difference of versions I strongly think is causing my problems..
When I run "cabal install bytestring" from the CLI, I get "resolving differences" ....
If my assertion that the "delta" between the "global" vs "local" is causing my compile problems, then what should I do??
Regards, Vasili
Warning: This package indirectly depends on multiple versions of the same
package. This is highly likely to cause a compile failure.
package binary-0.4.2 requires bytestring-0.9.0.1
package bio-0.3.4.1 requires bytestring-0.9.1.0
ah ha .. Ketil, this is what you are saying? If so, how do I fix? install a newer version of binary?
regards, vasiliOn Wed, Dec 3, 2008 at 1:32 AM, Ketil Malde <ketil@malde.org> wrote:
"Galchin, Vasili" <vigalchin@gmail.com> writes:You rarely need to import 'Internal' directly.
> I think I am getting a namespace collition between
>
> Data.ByteString.Lazy.Char8.ByteString
>
> and
>
> Data.ByteString.Lazy.Internal.ByteString ....
Are you sure this is not just a versioning problem? I.e. that some
> here is the error message ....
>
> Couldn't match expected type `B.ByteString'
> against inferred type
> `bytestring-0.9.0.1:Data.ByteString.Lazy.Internal.ByteString'
library is built against bytestring-0.X.Y, but your current import is
bytestring-0.A.B, but your program expects these to be the same? (And
they probably are, but the compiler can't really tell).
-k
--
If I haven't seen further, it is by standing in the footprints of giants