Build #2 for xml-verify-0.1.0.1
| Package | xml-verify-0.1.0.1 |
|---|
| Install | ConfigureFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2021-09-23 11:13:21.886787827 UTC |
|---|---|
| Compiler | ghc-8.10.2 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | base-4.14.1.0, bytestring-0.10.12.1, cryptostore-0.2.1.0, hxt-9.3.1.22, mtl-2.2.2, pem-0.2.4, x509-1.7.5 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Warning: The following packages are likely to be broken by the reinstalls: process-1.6.9.0 haskeline-0.8.0.1 ghc-8.10.2 Cabal-3.2.0.0 libiserv-8.10.2 ghci-8.10.2 directory-1.3.6.0 hpc-0.6.1.0 ghc-boot-8.10.2 Continuing even though the plan contains dangerous reinstalls. Starting data-default-class-0.1.2.0 Starting hourglass-0.2.12 Starting bytestring-0.10.12.1 Starting basement-0.0.12 Building data-default-class-0.1.2.0 Building hourglass-0.2.12 Building basement-0.0.12 Building bytestring-0.10.12.1 Completed data-default-class-0.1.2.0 Starting hxt-charproperties-9.5.0.0 Building hxt-charproperties-9.5.0.0 Completed hourglass-0.2.12 Starting th-compat-0.1.3 Building th-compat-0.1.3 Completed th-compat-0.1.3 Completed hxt-charproperties-9.5.0.0 Starting hxt-unicode-9.0.2.4 Building hxt-unicode-9.0.2.4 Completed hxt-unicode-9.0.2.4 Completed bytestring-0.10.12.1 Starting binary-0.8.9.0 Starting unix-2.7.2.2 Building binary-0.8.9.0 Building unix-2.7.2.2 Completed binary-0.8.9.0 Starting text-1.2.5.0 Building text-1.2.5.0 Completed basement-0.0.12 Starting memory-0.16.0 Building memory-0.16.0 Completed unix-2.7.2.2 Starting directory-1.3.7.0 Completed text-1.2.5.0 Starting parsec-3.1.14.0 Building directory-1.3.7.0 Building parsec-3.1.14.0 Completed directory-1.3.7.0 Completed memory-0.16.0 Starting pem-0.2.4 Starting asn1-types-0.3.4 Starting cryptonite-0.29 Completed parsec-3.1.14.0 Starting network-uri-2.6.4.1 Building pem-0.2.4 Building asn1-types-0.3.4 Building cryptonite-0.29 Building network-uri-2.6.4.1 Completed pem-0.2.4 Starting hxt-regex-xmlschema-9.2.0.7 Building hxt-regex-xmlschema-9.2.0.7 Completed asn1-types-0.3.4 Starting asn1-encoding-0.9.6 Building asn1-encoding-0.9.6 Completed network-uri-2.6.4.1 Completed hxt-regex-xmlschema-9.2.0.7 Starting hxt-9.3.1.22 Completed asn1-encoding-0.9.6 Starting asn1-parse-0.9.5 Building hxt-9.3.1.22 Building asn1-parse-0.9.5 Completed asn1-parse-0.9.5 Completed hxt-9.3.1.22 Completed cryptonite-0.29 Starting x509-1.7.5 Building x509-1.7.5 Completed x509-1.7.5 Starting x509-store-1.6.7 Building x509-store-1.6.7 Completed x509-store-1.6.7 Starting x509-validation-1.6.11 Building x509-validation-1.6.11 Completed x509-validation-1.6.11 Starting cryptostore-0.2.1.0 Building cryptostore-0.2.1.0 Completed cryptostore-0.2.1.0 Starting xml-verify-0.1.0.1 Failed to install xml-verify-0.1.0.1 Build log ( /home/builder/.cabal/logs/ghc-8.10.2/xml-verify-0.1.0.1-4A3EoqkIBg73vi0pcJ34De.log ): cabal: Entering directory '/tmp/cabal-tmp-15693/xml-verify-0.1.0.1' Configuring xml-verify-0.1.0.1... configure: WARNING: unrecognized options: --with-compiler checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for xmlsec1 >= 1.0.0... no cabal: Missing dependency on a foreign library: * Missing (or bad) C library: xmlsec1 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-15693/xml-verify-0.1.0.1' cabal: Error: some packages failed to install: xml-verify-0.1.0.1-4A3EoqkIBg73vi0pcJ34De failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.