Advertisement
Guest User

Untitled

a guest
Oct 4th, 2018
185
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.96 KB | None | 0 0
  1. -- While building custom Setup.hs for package digest-0.0.1.2 using:
  2. /home/sam/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_2.0.1.0_ghc-8.2.2 --builddir=.stack-work/dist/x86_64-linux/Cabal-2.0.1.0 configure --with-ghc=/home/sam/.nix-profile/bin/ghc --with-ghc-pkg=/home/sam/.nix-profile/bin/ghc-pkg --user --package-db=clear --package-db=global --package-db=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/pkgdb --libdir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/lib --bindir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/bin --datadir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/share --libexecdir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/libexec --sysconfdir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/etc --docdir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/doc/digest-0.0.1.2 --htmldir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/doc/digest-0.0.1.2 --haddockdir=/home/sam/.stack/snapshots/x86_64-linux/lts-11.6/8.2.2/doc/digest-0.0.1.2 --dependency=base=base-4.10.1.0 --dependency=bytestring=bytestring-0.10.8.2
  3. Process exited with code: ExitFailure 1
  4. Logs have been written to: /tmp/stack-upgrade4002/stack-1.7.1/.stack-work/logs/digest-0.0.1.2.log
  5. Configuring digest-0.0.1.2...
  6. Cabal-simple_mPHDZzAJ_2.0.1.0_ghc-8.2.2: Missing dependency on a foreign
  7. library:
  8. * Missing (or bad) header file: zlib.h
  9. * Missing C library: z
  10. This problem can usually be solved by installing the system package that
  11. provides this library (you may need the "-dev" version). If the library is
  12. already installed but in a non-standard location then you can use the flags
  13. --extra-include-dirs= and --extra-lib-dirs= to specify where it is.
  14. If the header file does exist, it may contain errors that are caught by the C
  15. compiler at the preprocessing stage. In this case you can re-run configure
  16. with the verbosity flag -v3 to see the error messages.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement