Build #1 for binary-strict-0.4.4

[all reports]

Package binary-strict-0.4.4
Install BuildFailed
Docs NotTried
Tests NotTried
Time submitted unknown
Compiler ghc-7.6.3
OS linux
Arch x86_64
Dependencies containers-0.5.0.0, bytestring-0.10.0.2, base-4.6.0.1, array-0.4.0.1
Flags none

Code Coverage

No Code Coverage was submitted for this report.

Build log

[view raw]

Resolving dependencies...
Downloading binary-strict-0.4.4...
Configuring binary-strict-0.4.4...
Building binary-strict-0.4.4...
Preprocessing library binary-strict-0.4.4...

src/Data/Binary/Strict/BitGet.hs:2:16: Warning:
    -fglasgow-exts is deprecated: Use individual extensions instead

src/Data/Binary/Strict/Get.hs:2:16: Warning:
    -fglasgow-exts is deprecated: Use individual extensions instead

src/Data/Binary/Strict/IncrementalGet.hs:2:16: Warning:
    -fglasgow-exts is deprecated: Use individual extensions instead
[1 of 9] Compiling Data.Binary.Strict.Util ( src/Data/Binary/Strict/Util.hs, dist/build/Data/Binary/Strict/Util.o )
[2 of 9] Compiling Data.Binary.Strict.Class ( src/Data/Binary/Strict/Class.hs, dist/build/Data/Binary/Strict/Class.o )

src/Data/Binary/Strict/Class.hs:54:20:
    Ambiguous occurrence `many'
    It could refer to either `Data.Binary.Strict.Class.many',
                             defined at src/Data/Binary/Strict/Class.hs:49:3
                          or `Control.Applicative.many',
                             imported from `Control.Applicative' at src/Data/Binary/Strict/Class.hs:7:28-42

src/Data/Binary/Strict/Class.hs:60:15:
    Ambiguous occurrence `many'
    It could refer to either `Data.Binary.Strict.Class.many',
                             defined at src/Data/Binary/Strict/Class.hs:49:3
                          or `Control.Applicative.many',
                             imported from `Control.Applicative' at src/Data/Binary/Strict/Class.hs:7:28-42
Failed to install binary-strict-0.4.4
cabal: Error: some packages failed to install:
binary-strict-0.4.4 failed during the building phase. The exception was:
ExitFailure 1

Test log

No test log was submitted for this report.