Build #2 for lame-0.2.2
Package | lame-0.2.2 |
---|
Install | ConfigureFailed |
---|---|
Docs | NotTried |
Tests | NotTried |
Time submitted | 2023-10-25 21:27:41.462713201 UTC |
---|---|
Compiler | ghc-9.2.4 |
OS | linux |
Arch | x86_64 |
Dependencies | base-4.16.3.0, bytestring-0.11.3.1, directory-1.3.6.2, exceptions-0.10.4, filepath-1.4.2.2, text-2.1, wave-0.2.1 |
Flags | -dev |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Starting data-array-byte-0.1.0.1 Starting cereal-0.5.8.3 Building data-array-byte-0.1.0.1 Building cereal-0.5.8.3 Completed data-array-byte-0.1.0.1 Starting text-2.1 Building text-2.1 Completed cereal-0.5.8.3 Starting wave-0.2.1 Building wave-0.2.1 Completed wave-0.2.1 Completed text-2.1 Starting lame-0.2.2 Failed to install lame-0.2.2 Build log ( /home/builder/.cabal/logs/ghc-9.2.4/lame-0.2.2-FJhAcPMYrqUCa3v6KZvRNI.log ): cabal: Entering directory '/tmp/cabal-tmp-1473970/lame-0.2.2' Configuring lame-0.2.2... Error: cabal-3.8.1.0: Missing dependency on a foreign library: * Missing (or bad) C library: mp3lame 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-1473970/lame-0.2.2' Error: cabal: Some packages failed to install: lame-0.2.2-FJhAcPMYrqUCa3v6KZvRNI failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.