2014-04-14 02:58:27 +0200 <nstdloop> even though I have cabal version "cabal-install version"
2014-04-14 02:58:14 +0200 <nstdloop> cabal: The package 'package' requires Cabal library version -any && >=1.10
2014-04-13 23:18:12 +0200 <Guest_> Is there an easy way to remove all the work done by a previous version of cabal working with a previous version of ghc?
2014-04-13 21:57:30 +0200 <conal> dcoutts: thanks again for the help. i'm back in business with a tolerable work-around, and hopefully Cabal's behavior will get refined. Filed https://github.com/haskell/cabal/issues/1773 .
2014-04-13 21:47:51 +0200 <conal> dcoutts: giving "-j1" to "cabal install" works, as you suggest (and I misunderstood).
2014-04-13 21:46:50 +0200 <conal> i hadn't noticed the cabal jobs flag.
2014-04-13 21:45:39 +0200 <dcoutts> conal: but I also think that newer cabal -j passes -j on to ghc as appropriate (iirc)
2014-04-13 21:43:29 +0200 <dcoutts> conal: it's not the ghc options, it's cabal's own parallel build
2014-04-13 21:43:22 +0200 <conal> dcoutts: Oh, hm. "cabal build" doesn't do it. Just "cabal install".
2014-04-13 21:42:58 +0200 <conal> dcoutts: I removed ghc-options:"-j" from my ~/.cabal/config and am still getting the "Last 10 lines ..." message. Are you sure that message is tied to -j?
2014-04-13 21:40:43 +0200 <nstdloop> dcoutts: Grabbed a binary from brew, so I now have the most up to date cabal but it still gives me the same error
2014-04-13 21:38:03 +0200 <dcoutts> nstdloop: or grab a binary, http://www.haskell.org/cabal/release/cabal-install-…
2014-04-13 21:37:06 +0200 <dcoutts> nstdloop: you can try bootstrapping cabal-install directly
2014-04-13 21:35:20 +0200 <dcoutts> nstdloop: check you're running cabal directly
2014-04-13 21:32:45 +0200 <dcoutts> nstdloop: doesn't look like it's a message from cabal
2014-04-13 21:32:29 +0200 <nstdloop> when doing cabal install cabal-install
2014-04-13 21:31:11 +0200 <dcoutts> nstdloop: upgrade cabal too
2014-04-13 21:30:53 +0200 <nstdloop> After updating ghc cabal fails at everything. I'm probably doing something silly - what do I have to change?
2014-04-13 21:20:44 +0200 <dcoutts> conal: oh definitely cabal
2014-04-13 21:20:32 +0200 <conal> dcoutts: thx. do you think it's a ghc issue or cabal or both or ...?
2014-04-13 21:11:30 +0200 <conal> hm. it's very convenient to have -j in .cabal/config, so i don't have to specify it repeatedly.
2014-04-13 21:10:29 +0200 <conal> dcoutts: oh! thanks. it's in my .cabal/config.
2014-04-13 21:09:01 +0200 <conal> In GHC 7.8.*, or maybe Cabal 1.18.*, a failing 'cabal build' yields "Last 10 lines of the build log ...", often cutting off the source position (filename & line & column #s). Emacs then can't jump directly to the error in the source. Are there solutions/workarounds?
2014-04-13 20:09:19 +0200 <Wizek_> Have anyone run into this? "ld: library not found for -lHSsetenv-" on OS X 10.9.1 while `cabal install`-ing?
2014-04-13 19:50:44 +0200 <Wizek_> Okay, successfully updated cabal and cabal-install, now I am trying to install hspec, but it gives me this error --> https://gist.github.com/Wizek/259d89d617416c9a29bd
2014-04-13 19:40:36 +0200 <Philonous> Very strange. I'm inside a sandbox, cabal install errors out with unsatisfiable dependencies, but when I run cabal install text first it goes through without a hitch
2014-04-13 19:37:43 +0200 <Ywen> Wizek_: (just don't forget the 'cabal update' before)
2014-04-13 19:37:20 +0200 <Ywen> Wizek_: next time I launch 'cabal install --only-dependencies'
2014-04-13 19:37:01 +0200 <Ywen> then cabal will reinstall everything I need next time I lau
2014-04-13 19:36:37 +0200 <Ywen> Wizek_: What I always do when I update GHC is remove my .cabal & .ghc directories (making sure before my .cabal/config and the 'cabal' executable are saved elsewhere)
2014-04-13 19:36:14 +0200 <geekosaur> best is to get all the old stuff out of $PATH and use the bootstrap install to install a new cabal-install against the newer ghc
2014-04-13 19:35:50 +0200 <geekosaur> if it was installed under an older one, it will be using the Cabal library from the older one and can become quite confused if it encounters a newer ghc
2014-04-13 19:35:31 +0200 <Wizek_> I am trying `cabal install cabal cabal-install `, and it spits out a lot of warnings
2014-04-13 19:35:18 +0200 <geekosaur> Wizek_, it generally depends on whether cabal-install knows about the newer ghc or not
2014-04-13 19:34:57 +0200 <Wizek_> oh, it could be that my cabal is outdated