[all reports]
Install |
ConfigureFailed |
Docs |
NotTried |
Tests |
NotTried |
Time submitted |
unknown
|
Compiler |
ghc-7.6.3 |
OS |
linux |
Arch |
x86_64 |
Dependencies |
unix-2.6.0.1, hBDD-0.0.2, deepseq-1.3.0.1, containers-0.5.0.0, base-4.6.0.1 |
Flags |
none
|
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies...
Configuring hBDD-0.0.2...
Building hBDD-0.0.2...
Preprocessing library hBDD-0.0.2...
[1 of 2] Compiling Data.Boolean ( Data/Boolean.hs, dist/build/Data/Boolean.o )
[2 of 2] Compiling Data.Boolean.BF ( Data/Boolean/BF.hs, dist/build/Data/Boolean/BF.o )
In-place registering hBDD-0.0.2...
Running Haddock for hBDD-0.0.2...
Running hscolour for hBDD-0.0.2...
Preprocessing library hBDD-0.0.2...
Preprocessing library hBDD-0.0.2...
Haddock coverage:
100% ( 18 / 18) in 'Data.Boolean'
Warning: Data.Boolean.BF: We do not support associated types in instances yet. These instances are affected:
Data.Boolean.QBF Data.Boolean.BF.BF, Data.Boolean.Substitution Data.Boolean.BF.BF
100% ( 3 / 3) in 'Data.Boolean.BF'
Documentation created: dist/doc/html/hBDD/index.html
Installing library in
/srv/hackage/var/build/tmp-install/lib/x86_64-linux-ghc-7.6.3/hBDD-0.0.2
Registering hBDD-0.0.2...
Installed hBDD-0.0.2
Configuring hBDD-CUDD-0.0.2...
cabal: Missing dependencies on foreign libraries:
* Missing (or bad) header file: cudd.h
* Missing C libraries: cudd, mtr, st, epd
This problem can usually be solved by installing the system packages that
provide these libraries (you may need the "-dev" versions). If the libraries
are already installed but in a non-standard location then you can use the
flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
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.
Failed to install hBDD-CUDD-0.0.2
cabal: Error: some packages failed to install:
hBDD-CUDD-0.0.2 failed during the configure step. The exception was:
ExitFailure 1