Build #2 for pipes-pulse-simple-0.1.0.0
Package | pipes-pulse-simple-0.1.0.0 |
---|
Install | DependencyFailed pipes-pulse-simple-0.1.0.0 |
---|---|
Docs | NotTried |
Tests | NotTried |
Time submitted | 2021-03-21 21:18:12.894663791 UTC |
---|---|
Compiler | ghc-8.10.2 |
OS | linux |
Arch | x86_64 |
Dependencies | base-4.14.1.0, bytestring-0.10.10.0, pipes-4.3.15, pipes-safe-2.3.3, pulse-simple-0.1.14 |
Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Starting pulse-simple-0.1.14 Starting primitive-0.7.1.0 Starting transformers-compat-0.6.6 Starting base-orphans-0.8.4 Building transformers-compat-0.6.6 Building primitive-0.7.1.0 Building base-orphans-0.8.4 Failed to install pulse-simple-0.1.14 Build log ( /home/builder/.cabal/logs/ghc-8.10.2/pulse-simple-0.1.14-Br4B8hRfPdS32xtPVj8eUK.log ): cabal: Entering directory '/tmp/cabal-tmp-15470/pulse-simple-0.1.14' Configuring pulse-simple-0.1.14... cabal: Missing dependency on a foreign library: * Missing (or bad) C library: pulse-simple 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. cabal: Leaving directory '/tmp/cabal-tmp-15470/pulse-simple-0.1.14' Starting void-0.7.3 Building void-0.7.3 Completed void-0.7.3 Completed transformers-compat-0.6.6 Completed base-orphans-0.8.4 Completed primitive-0.7.1.0 cabal: Error: some packages failed to install: pipes-pulse-simple-0.1.0.0-4vYdkQ0Og9REPdS72RGvwz depends on pipes-pulse-simple-0.1.0.0 which failed to install. pulse-simple-0.1.14-Br4B8hRfPdS32xtPVj8eUK failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.