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
Galchin, Vasili [EMAIL PROTECTED] writes:
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,
On Wed, 2008-12-03 at 01:52 -0600, Galchin, Vasili wrote:
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
Hello,
Some mention is made in corresponding web pages about implementation
difference of these three different DataString impl. Any advice?
Regards, Vasili
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
On Tue, 2008-12-02 at 17:43 -0600, Galchin, Vasili wrote:
Hello,
Some mention is made in corresponding web pages about
implementation difference of these three different DataString impl.
Any advice?
Perhaps you need to ask a more specific question.
Data.ByteString is a simple strict
I am getting a collision with Internal sigh.
vasili
On Tue, Dec 2, 2008 at 5:59 PM, Duncan Coutts
[EMAIL PROTECTED]wrote:
On Tue, 2008-12-02 at 17:43 -0600, Galchin, Vasili wrote:
Hello,
Some mention is made in corresponding web pages about
implementation difference of these
I think I am getting a namespace collition between
Data.ByteString.Lazy.Char8.ByteString
and
Data.ByteString.Lazy.Internal.ByteString
here is the error message
Couldn't match expected type `B.ByteString'
against inferred type
Galchin, Vasili [EMAIL PROTECTED] writes:
I think I am getting a namespace collition between
Data.ByteString.Lazy.Char8.ByteString
and
Data.ByteString.Lazy.Internal.ByteString
You rarely need to import 'Internal' directly.
here is the error message
Couldn't
On Wed, Dec 3, 2008 at 1:32 AM, Ketil Malde [EMAIL PROTECTED] wrote:
Galchin, Vasili [EMAIL PROTECTED] writes:
I think I am getting a namespace collition between
Data.ByteString.Lazy.Char8.ByteString
and
Data.ByteString.Lazy.Internal.ByteString
You rarely need to
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?
10 matches
Mail list logo