Build #7 for ipc-0.0.3
| Package | ipc-0.0.3 |
|---|
| Install | DependencyFailed network-bytestring-0.1.1.2 |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2017-01-03 16:40:52.244471 UTC |
|---|---|
| Compiler | ghc-8.0.1.20161018 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | base-4.9.0.0, binary-0.8.3.0, bytestring-0.10.8.1, dlist-0.8.0.2, mtl-2.2.1, network-2.6.3.1, network-bytestring-0.1.1.2, stm-2.4.4.1 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies...
Configuring call-stack-0.1.0...
Configuring dlist-0.8.0.2...
Building dlist-0.8.0.2...
Building call-stack-0.1.0...
Installed call-stack-0.1.0
Configuring mtl-2.2.1...
Building mtl-2.2.1...
Configuring network-2.6.3.1...
Installed dlist-0.8.0.2
Building network-2.6.3.1...
Configuring HUnit-1.5.0.0...
Installed mtl-2.2.1
Building HUnit-1.5.0.0...
Configuring stm-2.4.4.1...
Installed HUnit-1.5.0.0
Building stm-2.4.4.1...
Installed stm-2.4.4.1
Installed network-2.6.3.1
Configuring network-bytestring-0.1.1.2...
Building network-bytestring-0.1.1.2...
Failed to install network-bytestring-0.1.1.2
Build log ( /home/builder/.cabal/logs/network-bytestring-0.1.1.2.log ):
cabal: Entering directory '/tmp/cabal-tmp-19429/network-bytestring-0.1.1.2'
Configuring network-bytestring-0.1.1.2...
Building network-bytestring-0.1.1.2...
Preprocessing library network-bytestring-0.1.1.2...
[1 of 1] Compiling Network.Socket.ByteString ( dist/build/Network/Socket/ByteString.hs, dist/build/Network/Socket/ByteString.o )
Network/Socket/ByteString.cpphs:51:1: error:
Failed to load interface for ‘GHC.IOBase’
Perhaps you meant GHC.Base (from base-4.9.0.0)
Use -v to see a list of the files searched for.
cabal: Leaving directory '/tmp/cabal-tmp-19429/network-bytestring-0.1.1.2'
cabal: Error: some packages failed to install:
ipc-0.0.3 depends on network-bytestring-0.1.1.2 which failed to install.
network-bytestring-0.1.1.2 failed during the building phase. The exception
was:
ExitFailure 1
Test log
No test log was submitted for this report.