Build #3 for toxcore-c-0.2.11

[all reports]

Package toxcore-c-0.2.11
Install ConfigureFailed
Docs NotTried
Tests NotTried
Time submitted 2020-03-27 06:17:15.012424137 UTC
Compiler ghc-8.6.3
OS linux
Arch x86_64
Dependencies base-, bytestring-, data-default-class-, base-, base16-bytestring-, bytestring-, directory-
Flags none

Code Coverage

No Code Coverage was submitted for this report.

Build log

[view raw]

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:

Resolving dependencies...
Starting     base16-bytestring-
Starting     data-default-class-
Building     data-default-class-
Building     base16-bytestring-
Completed    data-default-class-
Completed    base16-bytestring-
Starting     toxcore-c-0.2.11
Failed to install toxcore-c-0.2.11
Build log ( /home/builder/.cabal/logs/ghc-8.6.3/toxcore-c-0.2.11-FCtWnQGWSxu4ha61puKaDT.log ):
cabal: Entering directory '/tmp/cabal-tmp-25323/toxcore-c-0.2.11'
Configuring toxcore-c-0.2.11...
cabal: Missing dependencies on foreign libraries:
* Missing (or bad) C libraries: toxcore, toxcore
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.

cabal: Leaving directory '/tmp/cabal-tmp-25323/toxcore-c-0.2.11'
cabal: Error: some packages failed to install:
toxcore-c-0.2.11-FCtWnQGWSxu4ha61puKaDT failed during the configure step. The
exception was:
ExitFailure 1

Test log

No test log was submitted for this report.