Why you want to build and install a bunch of libraries? You most
likely don't want to do that.
If you want to play with particular GHC version, create an
ordinary cabal package with dependencies you need, and point
`cabal-install` to use your
HOME/code/HEAD-22/_build/stage1/bin/ghc
There is nothing (noteworthy) special about `cabal repl -w
$HOME/code/HEAD-22/_build/stage1/bin/ghc`; as long as
`cabal-install` is concerned, it's just some GHC build.
- Oleg
Dear devs
I have thirty or so builds of GHC on my disk. Sometimes I want to use one build to build and install (for that build alone) a bunch of libraries. If I docabal install hspec -w $HOME/code/HEAD-22/_build/stage1/bin/ghcthen Cabal rightly warns me
Warning: The libraries were installed by creating a global GHC environmentfile at:/home/simonpj/.ghc/x86_64-linux-9.15.20260309/environments/default
The presence of such an environment file is likely to confuse or break otherQuestion: how can I install the libraries in the build tree for $HOME/code/HEAD-22?tools because it changes GHC's behaviour: it changes the default package setin ghc and ghci from its normal value (which is "all boot libraries"). GHCenvironment files are little-used and often not tested for.
After all, I think ghc-internal, base etc are all in that build-tree. Surely hspec can be too?
But how?
Thanks!
Simon
_______________________________________________ ghc-devs mailing list -- ghc-devs@haskell.org To unsubscribe send an email to ghc-devs-leave@haskell.org