Resolving dependencies...
Starting     binary-state-0.1.1
Starting     bindings-DSL-1.0.25
Starting     data-binary-ieee754-0.4.4
Starting     base-orphans-0.8.4
Building     binary-state-0.1.1
Building     bindings-DSL-1.0.25
Building     base-orphans-0.8.4
Building     data-binary-ieee754-0.4.4
Completed    bindings-DSL-1.0.25
Starting     data-default-class-0.1.2.0
Completed    data-binary-ieee754-0.4.4
Starting     dlist-1.0
Building     data-default-class-0.1.2.0
Completed    binary-state-0.1.1
Starting     failure-0.2.0.3
Building     dlist-1.0
Building     failure-0.2.0.3
Completed    data-default-class-0.1.2.0
Starting     monadloc-0.7.1
Completed    failure-0.2.0.3
Starting     network-3.1.0.1
Building     monadloc-0.7.1
Completed    base-orphans-0.8.4
Starting     old-locale-1.0.0.7
Completed    monadloc-0.7.1
Starting     random-1.1
Completed    dlist-1.0
Starting     regex-base-0.94.0.1
Building     old-locale-1.0.0.7
Building     random-1.1
Building     regex-base-0.94.0.1
Building     network-3.1.0.1
Completed    old-locale-1.0.0.7
Starting     transformers-compat-0.6.6
Building     transformers-compat-0.6.6
Completed    regex-base-0.94.0.1
Starting     utf8-string-1.0.2
Building     utf8-string-1.0.2
Completed    random-1.1
Starting     bindings-libzip-1.0.1
Failed to install bindings-libzip-1.0.1
Build log ( /home/builder/.cabal/logs/ghc-8.10.2/bindings-libzip-1.0.1-Hm6J4VBojFfnqqJdM3dO6.log ):
cabal: Entering directory '/tmp/cabal-tmp-7123/bindings-libzip-1.0.1'
Configuring bindings-libzip-1.0.1...
cabal: Missing dependency on a foreign library:
* Missing (or bad) header file: zip.h
* Missing (or bad) C library: zip
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.
If the header 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-7123/bindings-libzip-1.0.1'
Starting     data-default-instances-containers-0.0.1
Building     data-default-instances-containers-0.0.1
Completed    transformers-compat-0.6.6
Completed    data-default-instances-containers-0.0.1
Completed    utf8-string-1.0.2
Completed    network-3.1.0.1
cabal: Error: some packages failed to install:
LibZip-1.0.1-ZvbbEHBuJxAaEIcFHZ0NA depends on LibZip-1.0.1 which failed to
install.
bindings-libzip-1.0.1-Hm6J4VBojFfnqqJdM3dO6 failed during the configure step.
The exception was:
ExitFailure 1
hs-java-0.4.1-88tgcsakWkFMuDTr1bGph depends on hs-java-0.4.1 which failed to
install.