Build #1 for Chitra-0.2.2
| Package | Chitra-0.2.2 |
|---|
| Install | BuildFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | unknown |
|---|---|
| Compiler | ghc-7.6.3 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | network-2.4.1.2, mtl-2.1.2, bytestring-0.10.0.2, binary-0.5.1.1, base-4.6.0.1 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies...
Downloading Chitra-0.2.2...
Configuring Chitra-0.2.2...
Building Chitra-0.2.2...
Preprocessing executable 'Chitra' for Chitra-0.2.2...
[ 1 of 10] Compiling Utilities.ParseByteString ( Utilities/ParseByteString.hs, dist/build/Chitra/Chitra-tmp/Utilities/ParseByteString.o )
Utilities/ParseByteString.hs:35:60:
Could not deduce (Eq a) arising from a use of `/='
from the context (Num a)
bound by the type signature for
parseByteString :: Num a => [a] -> BS.ByteString -> [Int]
at Utilities/ParseByteString.hs:32:20-59
Possible fix:
add (Eq a) to the context of
the inferred type of cleanup :: [b] -> [b]
or the type signature for
parseByteString :: Num a => [a] -> BS.ByteString -> [Int]
In the first argument of `(.)', namely `(/= 0)'
In the first argument of `filter', namely `((/= 0) . fst)'
In the second argument of `(.)', namely `filter ((/= 0) . fst)'
Utilities/ParseByteString.hs:37:50:
Could not deduce (Eq a) arising from a use of `getActionList'
from the context (Num a)
bound by the type signature for
parseByteString :: Num a => [a] -> BS.ByteString -> [Int]
at Utilities/ParseByteString.hs:32:20-59
Possible fix:
add (Eq a) to the context of
the type signature for
parseByteString :: Num a => [a] -> BS.ByteString -> [Int]
In the first argument of `getActions', namely
`(getActionList list)'
In the expression: getActions (getActionList list)
In an equation for `actionList':
actionList = getActions (getActionList list)
Failed to install Chitra-0.2.2
cabal: Error: some packages failed to install:
Chitra-0.2.2 failed during the building phase. The exception was:
ExitFailure 1
Test log
No test log was submitted for this report.