Thank you all. Everything is great now. It was because (Just ghcPath) was
not passed into runGhc, and lack of ghc-path.
peace and happiness,
-lyndon
2008/9/28 Thorkil Naur
On Sunday 28 September 2008 19:27, humasect wrote:
Ah, indeed it does! Then, more about GHC API: "Shell: Shell: missing -B<dir> option"
I can't find any information of what this -B is, it is not in GHC sources or anything helpful from google.
The -B is used from a ghc shell script to identify where the rest of the GHC installation resides. An example with a GHC 6.8.2 installed in $HOME/tn/install/ghc-6.8.2:
tn@linux:~> cat tn/install/ghc-6.8.2/bin/ghc #!/bin/sh GHCBIN=/home/tn/tn/install/ghc-6.8.2/lib/ghc-6.8.2/ghc-6.8.2 TOPDIROPT=-B/home/tn/tn/install/ghc-6.8.2/lib/ghc-6.8.2 exec $GHCBIN $TOPDIROPT ${1+"$@"} tn@linux:~>
There is likely some designation for this option that I cannot recall. If it is documented anywhere, I haven't noticed.
...
Best regards Thorkil
Thank you all. Everything is great now. It was because (Just ghcPath) was not passed into runGhc, and lack of ghc-path.
btw: is ghc-path going to be part of the ghc release or the haskell platform? Currently, I can't see it in either, which would be a pity. I thought the idea was to provide it in the ghc release, but not install it (since cabal install isn't going to be part of the ghc release after all). Claus
Claus Reinke wrote:
Thank you all. Everything is great now. It was because (Just ghcPath) was not passed into runGhc, and lack of ghc-path.
btw: is ghc-path going to be part of the ghc release or the haskell platform? Currently, I can't see it in either, which would be a pity. I thought the idea was to provide it in the ghc release, but not install it (since cabal install isn't going to be part of the ghc release after all).
I don't think we use ghc-paths in GHC's Haddock now (Ian - correct me if I'm wrong). And it's hard to provide ghc-paths with a GHC installation, because it would have to be built at install-time, or at least binary-patched. So I think we decided it was easiest to just let the user install it with cabal-install later. Cheers, Simon
On Tue, Sep 30, 2008 at 04:20:59PM +0100, Simon Marlow wrote:
Claus Reinke wrote:
Thank you all. Everything is great now. It was because (Just ghcPath) was not passed into runGhc, and lack of ghc-path.
btw: is ghc-path going to be part of the ghc release or the haskell platform? Currently, I can't see it in either, which would be a pity. I thought the idea was to provide it in the ghc release, but not install it (since cabal install isn't going to be part of the ghc release after all).
I don't think we use ghc-paths in GHC's Haddock now (Ian - correct me if I'm wrong).
You are right. Thanks Ian
participants (4)
-
Claus Reinke -
humasect -
Ian Lynagh -
Simon Marlow