*** setup configure Configuring Win32-2.2.0.2... Dependency base >=3 && <5: using base-4.3.1.0 Dependency bytestring -any: using bytestring-0.9.1.10 Using Cabal-1.10.2.0 compiled by ghc-7.0 Using compiler: ghc-7.0.4 Using install prefix: /usr/local/tmp/archive/install Binaries installed in: /usr/local/tmp/archive/install/bin Libraries installed in: /usr/local/tmp/archive/install/lib/Win32-2.2.0.2/ghc-7.0.4 Private binaries installed in: /usr/local/tmp/archive/install/libexec Data files installed in: /usr/local/tmp/archive/install/share/Win32-2.2.0.2 Documentation installed in: /usr/local/tmp/archive/install/share/doc/Win32-2.2.0.2 Using alex version 2.3.3 found on system at: /usr/bin/alex Using ar found on system at: /usr/bin/ar Using c2hs version 0.16.0 found on system at: /usr/local/bin/c2hs Using cpphs version 1.11 found on system at: /usr/local/bin/cpphs Using ffihugs found on system at: /usr/local/bin/ffihugs Using gcc version 4.5.3 found on system at: /usr/bin/gcc Using ghc version 7.0.4 found on system at: /usr/local/bin/ghc Using ghc-pkg version 7.0.4 found on system at: /usr/local/bin/ghc-pkg No greencard found Using haddock version 2.9.2 found on system at: /usr/local/bin/haddock Using happy version 1.18.6 found on system at: /usr/local/bin/happy No hmake found Using hsc2hs version 0.67 found on system at: /usr/local/bin/hsc2hs Using hscolour version 1.17 found on system at: /usr/local/bin/HsColour Using hugs found on system at: /usr/local/bin/hugs No jhc found Using ld found on system at: /usr/bin/ld No lhc found No lhc-pkg found No nhc98 found Using pkg-config version 0.26 found on system at: /usr/bin/pkg-config Using ranlib found on system at: /usr/bin/ranlib Using strip found on system at: /usr/bin/strip Using tar found on system at: /bin/tar No uhc found cabal-setup: Missing dependencies on foreign libraries: * Missing (or bad) header file: HsWin32.h * Missing C libraries: user32, gdi32, winmm, advapi32, shell32, shfolder 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.