Build #2 for network-fancy-0.1
| Package | network-fancy-0.1 |
|---|
| Install | ConfigureFailed |
|---|---|
| Docs | NotTried |
| Tests | NotTried |
| Time submitted | 2015-06-05 19:33:49.806819 UTC |
|---|---|
| Compiler | ghc-7.8.3 |
| OS | linux |
| Arch | x86_64 |
| Dependencies | random-1.1, directory-1.2.1.0, bytestring-0.10.4.0, base-4.7.0.1 |
| Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... Configuring random-1.1... Building random-1.1... Preprocessing library random-1.1... [1 of 1] Compiling System.Random ( System/Random.hs, dist/build/System/Random.o ) In-place registering random-1.1... Running Haddock for random-1.1... Running hscolour for random-1.1... Preprocessing library random-1.1... Preprocessing library random-1.1... Haddock coverage: Cannot find documentation for: $intro 100% ( 16 / 16) in 'System.Random' Documentation created: dist/doc/html/random/index.html, dist/doc/html/random/random.txt Creating package registration file: /tmp/pkgConf-random-131386.1 Installing library in /home/builder/hackage-server/build-cache/tmp-install/lib/x86_64-linux-ghc-7.8.3/random-1.1 Registering random-1.1... Installed random-1.1 Downloading network-fancy-0.1... Configuring network-fancy-0.1... cabal: Missing dependency on a foreign library: * Missing (or bad) header file: network-fancy.h 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 network-fancy-0.1 cabal: Error: some packages failed to install: network-fancy-0.1 failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.