Resolving dependencies... Downloading pcap-0.4.5.2... Configuring pcap-0.4.5.2... configure: WARNING: unrecognized options: --with-gcc checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for struct sockaddr.sa_len... no configure: creating ./config.status config.status: creating pcap.buildinfo config.status: creating include/pcapconfig.h config.status: include/pcapconfig.h is unchanged configure: WARNING: unrecognized options: --with-gcc cabal: Missing dependency on a foreign library: * Missing (or bad) header file: pcap.h * Missing C library: pcap 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 pcap-0.4.5.2 cabal: Error: some packages failed to install: hsns-0.5.3 depends on pcap-0.4.5.2 which failed to install. pcap-0.4.5.2 failed during the configure step. The exception was: ExitFailure 1