Build #1 for binaryen-0.0.1.0
| Package | binaryen-0.0.1.0 |
|---|
| Install | ConfigureFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2020-04-25 14:54:31.649147147 UTC |
|---|---|
| Compiler | ghc-8.6.3 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | base-4.12.0.0 |
| 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... Downloading binaryen-0.0.1.0 Downloaded binaryen-0.0.1.0 Starting binaryen-0.0.1.0 Failed to install binaryen-0.0.1.0 Build log ( /home/builder/.cabal/logs/ghc-8.6.3/binaryen-0.0.1.0-GzdfSUwebYo5HTDzTSQRJz.log ): cabal: Entering directory '/tmp/cabal-tmp-29160/binaryen-0.0.1.0' Configuring binaryen-0.0.1.0... cabal: Missing dependency on a foreign library: * Missing (or bad) C library: binaryen 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-29160/binaryen-0.0.1.0' cabal: Error: some packages failed to install: binaryen-0.0.1.0-GzdfSUwebYo5HTDzTSQRJz failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.