Actually it's not a problem with the version of haskell-src-meta but rather with the version of its dependency th-orphans. haskell-src-meta (versions 0.6.0.8 and 0.6.0.9) has an upper bound th-orphans <0.12. With --allow-newer you told Cabal to ignore version upper bounds, so Cabal decided to use th-orphans version 0.12.0, since it's...
You can use cntlm to talk to proxy. It will handle authentication issues. After configuring and installing cntlm, set up the new environmental variable by modifying http_proxy, https_proxy etc. Your cabal command should work after that....
haskell,cabal,cabal-install,stackage
The reason of the problem was that my GHC was too old. I downloaded a newer version and solved the problem. Failed (and wrong) attempt You should have a cabal.config file in your current directory. Open it with any text editor and serach for the transformers installed string. Once you...
haskell,cabal,haskell-platform,cabal-install
By configure, it's referring to the options that can be set before building the program. You can read these by running: cabal configure --help These include things like: --prefix the destination directory and --extra-lib-dirs : object code libraries to link against when compiling These two examples are similar to options...
haskell,yesod,cabal-install,nixos
I was able to get this working after using the method on O'Charles' Nix wiki. I have not determined why this method was not working before. Basically, first run cabal2nix. Then create a generic shell.nix (that can be shared between all Haskell packages). $ cabal2nix --jailbreak --sha256=X ./$cabal > default.nix...
@user2407038 was right, the exit code 9 is caused by running out of memory. Upgrading the ram on the VPS fixed the issue.
This issue is because of an old version of ghc-7.0.4.I downloaded ghc 7.8.3 source tarball from here and installed it. Then ghc 7.8.3 had old version of cabal so, have to unregister it from ghc 7.8.3 using ghc unregister Cabal . Then run bootstrap.sh from cabal-install-1.20 folder and got cabal-install...
haskell,shared-libraries,cabal,cabal-install
Does using just one sandbox work for you? (unpack A into src/A) (unpack B into src/B) cd src/B cabal sandbox init cabal add-source ../src/A cabal install -- builds both A and B Now there is only one sandbox (located in src/B)....
haskell,cabal,cabal-install,c2hs
You need to add Test to the other-modules field.
haskell,cabal,cabal-install,nix,haskell-ng
Could someone please explain what haskellng is in a simple, clear way? Well, haskellng is the next generation Nix Haskell package set made for Nix. I think most of the work was done by Peter Simons. But note that in the latest master version, haskellngPackages has been renamed back...
cabal-install is sensitive to the ordering of the command line flags respective to the subcommands. --no-require-sanbox is a global flag that applies to all subcommands, not just to install, so you need to put it before install: $ cabal --no-require-sandbox install ... ...
Error : checking whether we are cross compiling... configure: error: in `/tmp/network-2.5.0.023068/network-2.5.0.0': configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details So, I run command yum groupinstall "development tools", installed c compiler tools and could compile c programs. Then,...
haskell,install,cabal,cabal-install,hackage
I have finally figured out the solution. Rajarshi is right for the locale problem. However, changing the locale temporarily won't work. The package now correctly installed after changing the locale permanently. How to check the current locale setting $ locale If you notice that LANG is C or empty, probably...
haskell,configuration,ghc,cabal,cabal-install
Okay, I decided to just look at the source code and answer my own question. After diving through the cabal-install source code and ending up inside the GHC source I eventually found what I was looking for at the bottom of compiler/main/HscMain.hs: showModuleIndex :: (Int, Int) -> String showModuleIndex (i,n)...
Not quite. At the moment, anything in the global package database is also used by sandboxes. I believe future versions of cabal-install will restrict this to a few whitelisted core packages that ship with GHC (and that shouldn't/can't be replaced anyway).