Resolving dependencies...
Configuring cereal-0.4.0.1...
Building cereal-0.4.0.1...
Preprocessing library cereal-0.4.0.1...
[1 of 5] Compiling Data.Serialize.Builder ( src/Data/Serialize/Builder.hs, dist/build/Data/Serialize/Builder.o )
[2 of 5] Compiling Data.Serialize.Put ( src/Data/Serialize/Put.hs, dist/build/Data/Serialize/Put.o )
[3 of 5] Compiling Data.Serialize.Get ( src/Data/Serialize/Get.hs, dist/build/Data/Serialize/Get.o )
[4 of 5] Compiling Data.Serialize.IEEE754 ( src/Data/Serialize/IEEE754.hs, dist/build/Data/Serialize/IEEE754.o )
[5 of 5] Compiling Data.Serialize   ( src/Data/Serialize.hs, dist/build/Data/Serialize.o )
In-place registering cereal-0.4.0.1...
Running Haddock for cereal-0.4.0.1...
Running hscolour for cereal-0.4.0.1...
Preprocessing library cereal-0.4.0.1...
Preprocessing library cereal-0.4.0.1...
Warning: The documentation for the following packages are not installed. No
links will be generated to these packages: rts-1.0
Haddock coverage:
  96% ( 26 / 27) in 'Data.Serialize.Builder'
  69% ( 29 / 42) in 'Data.Serialize.Put'
  94% ( 50 / 53) in 'Data.Serialize.Get'
 100% ( 11 / 11) in 'Data.Serialize.IEEE754'
Cannot find documentation for: $example
 100% ( 11 / 11) in 'Data.Serialize'
Warning: Data.Serialize.Put: could not find link destinations for:
    Data.Serialize.Put.PairS
Warning: Data.Serialize.Get: could not find link destinations for:
    Data.Serialize.Get.get
Documentation created: dist/doc/html/cereal/index.html
Installing library in
/srv/hackage/var/build/tmp-install/lib/cereal-0.4.0.1/ghc-7.6.3
Registering cereal-0.4.0.1...
Installed cereal-0.4.0.1
Downloading arbb-vm-0.1.1.20...
Configuring arbb-vm-0.1.1.20...
cabal: Missing dependency on a foreign library:
* Missing (or bad) header file: arbb_vmapi.h
* Missing C library: arbb_dev
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 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.
Failed to install arbb-vm-0.1.1.20
cabal: Error: some packages failed to install:
arbb-vm-0.1.1.20 failed during the configure step. The exception was:
ExitFailure 1