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...
Starting     clock-0.8
Starting     managed-1.0.6
Starting     sorted-list-0.2.1.0
Building     managed-1.0.6
Building     clock-0.8
Building     sorted-list-0.2.1.0
Completed    managed-1.0.6
Completed    sorted-list-0.2.1.0
Completed    clock-0.8
Starting     grpc-haskell-core-0.0.0.0
Failed to install grpc-haskell-core-0.0.0.0
Build log ( /home/builder/.cabal/logs/ghc-8.6.3/grpc-haskell-core-0.0.0.0-GtG9PQluc1GDO8qm4yqIBM.log ):
cabal: Entering directory '/tmp/cabal-tmp-6841/grpc-haskell-core-0.0.0.0'
Configuring grpc-haskell-core-0.0.0.0...
cabal: Missing dependencies on foreign libraries:
* Missing (or bad) header file: include/grpc_haskell.h
* Missing (or bad) C libraries: grpc, gpr
This problem can usually be solved by installing the system packages that
provide these libraries (you may need the "-dev" versions). If the libraries
are already installed but in a non-standard location then you can use the
flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.If
the library files do 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-6841/grpc-haskell-core-0.0.0.0'
cabal: Error: some packages failed to install:
grpc-haskell-core-0.0.0.0-GtG9PQluc1GDO8qm4yqIBM failed during the configure
step. The exception was:
ExitFailure 1