I’m trying to follow the instructions for https://ghc.haskell.org/trac/ghc/ticket/12562 But I get cabal new-build llvm-general --with-ghc=/home/simonpj/5builds/HEAD-4/inplace/bin/ghc-stage2 cabal: unrecognised command: new-build (try --help) simonpj@cam-05-unx:~/tmp/llvm-general$ Maybe my Cabal is too old. I tried bash$ cabal install Cabal Resolving dependencies... Downloading Cabal-1.24.0.0... Configuring Cabal-1.24.0.0... Building Cabal-1.24.0.0... Installed Cabal-1.24.0.0 That worked. But I get the same message. Alas bash$ cabal --version cabal-install version 1.23.0.0 compiled using version 1.23.1.0 of the Cabal library bash$ which cabal /home/simonpj/.cabal/bin/cabal Maybe I need 1.24. Which claims to be installed. But WHERE is it installed? Thanks Simon
Simon Peyton Jones via ghc-devs
I’m trying to follow the instructions for https://ghc.haskell.org/trac/ghc/ticket/12562 But I get
cabal new-build llvm-general --with-ghc=/home/simonpj/5builds/HEAD-4/inplace/bin/ghc-stage2
cabal: unrecognised command: new-build (try --help)
Indeed new-build is a new feature of cabal-install 1.24.
simonpj@cam-05-unx:~/tmp/llvm-general$ Maybe my Cabal is too old. I tried
bash$ cabal install Cabal
Resolving dependencies...
Downloading Cabal-1.24.0.0...
Configuring Cabal-1.24.0.0...
Building Cabal-1.24.0.0...
Installed Cabal-1.24.0.0 That worked. But I get the same message. Alas
It's terribly confusing but the `cabal` executable is provided by the `cabal-install` package. Try `cabal install cabal-install`. Cheers, - Ben
On Mon, Sep 5, 2016 at 12:40 PM, Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote:
bash$ which cabal
/home/simonpj/.cabal/bin/cabal
Maybe I need 1.24. Which claims to be installed. But WHERE is it installed?
Try "type cabal". "which" has a nasty tendency to show you what the next shell you open (or sometimes the next time you login) will see; shells remember what they've already seen, so it's probably still running the old one (likely in /usr/bin or /usr/local/bin). POSIX requires "type" to show what the *current* shell (thinks it) knows, not what some future shell will see. "hash -r" should work to reset the shell's idea of where cabal is, if "type" says it's running a different cabal. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Thanks Brandon. But I think Ben was probably right; I need cabal install cabal-install. Somehow this ought to be easier.
I’ll try that when I next get a chance
SImion
From: Brandon Allbery [mailto:allbery.b@gmail.com]
Sent: 05 September 2016 17:50
To: Simon Peyton Jones
participants (3)
-
Ben Gamari -
Brandon Allbery -
Simon Peyton Jones