cabal appears to complain about relative paths #832

bos opened this Issue May 24, 2012 · 1 comment


None yet

1 participant

Haskell member

(Imported from Trac #842, reported by jeffz on 2011-05-16)

With cabal configure --extra-lib-dirs=foo

$ cabal build
Preprocessing library HENet-0.0.1...
Building HENet-0.0.1...
Registering HENet-0.0.1...
cabal.exe: HENet-0.0.1: library-dirs: .libs is a relative path (use --force to

Originally reported on irc:

<dcoutts> jeffz: the right solution here would be for cabal to make the paths absolute before passing them on to ghc-pkg

Haskell member

(Imported comment by MikolajKonarski on 2011-05-16)

It wouldn't hurt to allow relative paths to the compiler, too. Right now the following fails:

cabal install -w ../ghc.bkp/inplace/bin/ghc-stage2 parallel
Resolving dependencies...
Configuring containers-
cabal: Cannot find the program 'ghc' at '../ghc.bkp/inplace/bin/ghc-stage2' or on the path
but the same compilation works OK if installing from a source directory, not from Hackage.

BTW, If/when it's done, it would make sense to remove the tip about absolute paths, I've added in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment