Build #2 for SecureHash-SHA3-0.1.0.0
| Package | SecureHash-SHA3-0.1.0.0 |
|---|
| Install | BuildFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2018-11-30 23:03:52.33712746 UTC |
|---|---|
| Compiler | ghc-8.6.1 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | base-4.12.0.0, bytestring-0.10.8.2 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Warning: The install command is a part of the legacy v1 style of cabal usage.
Please switch to using either the new project style and the new-install
command or the legacy v1-install alias as new-style projects will become the
default in the next version of cabal-install. Please file a bug if you cannot
replicate a working v1- use case with the new-style commands.
For more information, see: https://wiki.haskell.org/Cabal/NewBuild
Resolving dependencies...
Starting SecureHash-SHA3-0.1.0.0
Building SecureHash-SHA3-0.1.0.0
Failed to install SecureHash-SHA3-0.1.0.0
Build log ( /home/builder/.cabal/logs/ghc-8.6.1/SecureHash-SHA3-0.1.0.0-HyHrlmrWYPL2oi9HME6RBZ.log ):
cabal: Entering directory '/tmp/cabal-tmp-24332/SecureHash-SHA3-0.1.0.0'
Configuring SecureHash-SHA3-0.1.0.0...
Preprocessing library for SecureHash-SHA3-0.1.0.0..
Building library for SecureHash-SHA3-0.1.0.0..
[1 of 2] Compiling Crypto.SecureHash.SHA3.FFI ( src/Crypto/SecureHash/SHA3/FFI.hs, dist/build/Crypto/SecureHash/SHA3/FFI.o )
In file included from /tmp/ghc24458_0/ghc_3.c:7:0: error:
cbits/CTS_SHA3.h:197:2: error:
error: #error "This C code currently assumes a CLANG / GCC compatible cpp env"
#error "This C code currently assumes a CLANG / GCC compatible cpp env"
^
|
197 | #error "This C code currently assumes a CLANG / GCC compatible cpp env"
| ^
`gcc' failed in phase `C Compiler'. (Exit code: 1)
cabal: Leaving directory '/tmp/cabal-tmp-24332/SecureHash-SHA3-0.1.0.0'
cabal: Error: some packages failed to install:
SecureHash-SHA3-0.1.0.0-HyHrlmrWYPL2oi9HME6RBZ failed during the building
phase. The exception was:
ExitFailure 1
Test log
No test log was submitted for this report.