Build #2 for nettle-0.3.1.1
| Package | nettle-0.3.1.1 |
|---|
| Install | ConfigureFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2024-02-12 22:07:18.720774981 UTC |
|---|---|
| Compiler | ghc-9.6.3 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | base-4.18.1.0, byteable-0.1.1, bytestring-0.11.5.2, crypto-cipher-types-0.0.9, securemem-0.1.10, tagged-0.8.8 |
| Flags | -usepkgconfig |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Starting byteable-0.1.1 Starting tagged-0.8.8 Starting basement-0.0.16 Building byteable-0.1.1 Building tagged-0.8.8 Building basement-0.0.16 Completed byteable-0.1.1 Completed tagged-0.8.8 Completed basement-0.0.16 Starting memory-0.18.0 Building memory-0.18.0 Completed memory-0.18.0 Starting securemem-0.1.10 Building securemem-0.1.10 Completed securemem-0.1.10 Starting crypto-cipher-types-0.0.9 Building crypto-cipher-types-0.0.9 Completed crypto-cipher-types-0.0.9 Starting nettle-0.3.1.1 Failed to install nettle-0.3.1.1 Build log ( /home/builder/.cabal/logs/ghc-9.6.3/nettle-0.3.1.1-3KewhmeGAkD26kVeolNj6O.log ): cabal: Entering directory '/tmp/cabal-tmp-1616077/nettle-0.3.1.1' Configuring nettle-0.3.1.1... Error: cabal-3.10.2.1: Missing dependency on a foreign library: * Missing (or bad) C library: nettle 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-1616077/nettle-0.3.1.1' Error: cabal: Some packages failed to install: nettle-0.3.1.1-3KewhmeGAkD26kVeolNj6O failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.