Build #8 for TrieMap-0.5.2
| Package | TrieMap-0.5.2 |
|---|
| Install | BuildFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2016-12-31 05:34:05.258985 UTC |
|---|---|
| Compiler | ghc-8.0.1.20161018 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | array-0.5.1.1, base-4.9.0.0, bytestring-0.10.8.1, containers-0.5.7.1, multirec-0.7.7, template-haskell-2.11.0.0 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies...
Configuring multirec-0.7.7...
Building multirec-0.7.7...
Installed multirec-0.7.7
Downloading TrieMap-0.5.2...
Configuring TrieMap-0.5.2...
Building TrieMap-0.5.2...
Failed to install TrieMap-0.5.2
Build log ( /home/builder/.cabal/logs/TrieMap-0.5.2.log ):
cabal: Entering directory '/tmp/cabal-tmp-18518/TrieMap-0.5.2'
Configuring TrieMap-0.5.2...
Building TrieMap-0.5.2...
Preprocessing library TrieMap-0.5.2...
[ 1 of 49] Compiling Data.TrieMap.Sized ( Data/TrieMap/Sized.hs, dist/build/Data/TrieMap/Sized.o )
[ 2 of 49] Compiling Data.TrieMap.Rep ( Data/TrieMap/Rep.hs, dist/build/Data/TrieMap/Rep.o )
Data/TrieMap/Rep.hs:9:1: warning: [-Wtabs]
Tab character found here, and in 11 further locations.
Please use spaces instead.
Data/TrieMap/Rep.hs:24:9: warning: [-Winline-rule-shadowing]
Rule "toRep/fromRep" may never fire
because rule "Class op fromRep" for ‘fromRep’ might fire first
Probable fix: add phase [n] or [~n] to the competing rule
[ 3 of 49] Compiling Data.TrieMap.Rep.TH ( Data/TrieMap/Rep/TH.hs, dist/build/Data/TrieMap/Rep/TH.o )
Data/TrieMap/Rep/TH.hs:33:13: error:
• The constructor ‘InstanceD’ should have 4 arguments, but has been given 3
• In the pattern: InstanceD cxt (reprt `AppT` f) _
In the pattern: InstanceD cxt (reprt `AppT` f) _ : _
In a stmt of a 'do' block:
iT@(InstanceD cxt (reprt `AppT` f) _ : _) <- decs
cabal: Leaving directory '/tmp/cabal-tmp-18518/TrieMap-0.5.2'
cabal: Error: some packages failed to install:
TrieMap-0.5.2 failed during the building phase. The exception was:
ExitFailure 1
Test log
No test log was submitted for this report.