Build #3 for boolector-0.0.0.1
| Package | boolector-0.0.0.1 |
|---|
| Install | ConfigureFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2018-06-19 05:00:13.93331637 UTC |
|---|---|
| Compiler | ghc-8.2.2 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | base-4.10.1.0, containers-0.5.10.2, mtl-2.2.1 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Configuring boolector-0.0.0.1... Failed to install boolector-0.0.0.1 Build log ( /home/builder/.cabal/logs/ghc-8.2.2/boolector-0.0.0.1-6mS8oIsI8XiKxnLR7jL5KY.log ): cabal: Entering directory '/tmp/cabal-tmp-32684/boolector-0.0.0.1' Configuring boolector-0.0.0.1... cabal: Missing dependency on a foreign library: * Missing (or bad) header file: boolector.h * Missing (or bad) C library: boolector This problem can usually be solved by installing the system package that provides this library (you may need the "-dev" version). If the library is already installed but in a non-standard location then you can use the flags --extra-include-dirs= and --extra-lib-dirs= to specify where it is.If the library file does exist, it may contain errors that are caught by the C compiler at the preprocessing stage. In this case you can re-run configure with the verbosity flag -v3 to see the error messages. If the header file does exist, it may contain errors that are caught by the C compiler at the preprocessing stage. In this case you can re-run configure with the verbosity flag -v3 to see the error messages. cabal: Leaving directory '/tmp/cabal-tmp-32684/boolector-0.0.0.1' cabal: Error: some packages failed to install: boolector-0.0.0.1-6mS8oIsI8XiKxnLR7jL5KY failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.