Build #9 for Win32-2.1
Package | Win32-2.1 |
---|
Install | ConfigureFailed |
---|---|
Docs | NotTried |
Tests | NotTried |
Time submitted | 2016-11-11 19:04:02.605609 UTC |
---|---|
Compiler | ghc-8.0.1.20161018 |
OS | linux |
Arch | x86_64 |
Dependencies | base-4.9.0.0 |
Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Resolving dependencies... cabal: Entering directory '/tmp/cabal-tmp-25853/Win32-2.1' [1 of 1] Compiling Main ( /tmp/cabal-tmp-25853/Win32-2.1/dist/setup/setup.hs, /tmp/cabal-tmp-25853/Win32-2.1/dist/setup/Main.o ) Linking /tmp/cabal-tmp-25853/Win32-2.1/dist/setup/setup ... Configuring Win32-2.1... Warning: No 'build-type' specified. If you do not need a custom Setup.hs or ./configure script then use 'build-type: Simple'. Warning: 'include-dirs: include' directory does not exist. setup: Missing dependencies on foreign libraries: * Missing (or bad) header file: HsWin32.h * Missing C libraries: user32, gdi32, winmm, kernel32, advapi32 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 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-25853/Win32-2.1' Failed to install Win32-2.1 cabal: Error: some packages failed to install: Win32-2.1 failed during the configure step. The exception was: ExitFailure 1
Test log
No test log was submitted for this report.