Build #2 for hscdio-0.1.0.0
| Package | hscdio-0.1.0.0 |
|---|
| Install | ConfigureFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2021-06-05 02:41:05.894736838 UTC |
|---|---|
| Compiler | ghc-8.10.2 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | base-4.14.1.0, bitwise-1.0.0.1, bytestring-0.10.10.0, containers-0.6.2.1, mtl-2.2.2, text-1.2.3.2, vector-0.12.3.0 |
| Flags | -dev -tools |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Starting bitwise-1.0.0.1 Starting primitive-0.7.1.0 Building bitwise-1.0.0.1 Building primitive-0.7.1.0 Completed bitwise-1.0.0.1 Completed primitive-0.7.1.0 Starting vector-0.12.3.0 Building vector-0.12.3.0 Completed vector-0.12.3.0 Starting hscdio-0.1.0.0 Failed to install hscdio-0.1.0.0 Build log ( /home/builder/.cabal/logs/ghc-8.10.2/hscdio-0.1.0.0-1anYTOz5zc9AJfSkqMUaKO.log ): cabal: Entering directory '/tmp/cabal-tmp-27408/hscdio-0.1.0.0' Configuring hscdio-0.1.0.0... cabal: Missing dependency on a foreign library: * Missing (or bad) header file: cdio/cdtext.h * Missing (or bad) C library: cdio 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-27408/hscdio-0.1.0.0' cabal: Error: some packages failed to install: hscdio-0.1.0.0-1anYTOz5zc9AJfSkqMUaKO failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.