You can clone with
(Imported from Trac #24, reported by @jgoerzen on 2005-11-28)
Cabal should not attempt to do anything relating to GHCI on archs that don't support it. It shouldn't try to build ghci libs, and it shouldn't pass --auto-ghci-libs to ghc-pkg.
More information here:
(Imported comment by @syntaxpolice on 2005-11-28)
clarification: newer cabal versions don't use --auto-ghci-libs and only try to build these libs during build time, not during compile time.
Here's what simon says about discovering whether we are on a platform with ghci:
(Imported comment by @dcoutts on 2005-12-10)
ghc-6.8 has a flag that tells us various features about the ghc installation. I think that the ghci support is one of these things. So we could support this feature in ghc-6.8 and later.
If we do this, should we drop the existing --disable-library-for-ghci flag? We could keep it if we tried the ghc -e "return ()" suggestion.
(Imported comment by @dcoutts on 2007-12-30)
This is pretty easy bug but it does not seem to bother anybody enough to fix it or even comment on it. Punting.
(Imported comment by @dcoutts on 2007-09-12)
Implementing this just for ghc 6.8 and later should be easy since we can parse the output of ghc --info to find the:
That should be used to set the default of whether ghci libs are built or not. Perhaps if the user explicitly asks for them and they cannot be supported there should be a warning.
Nothing activity in 6 years, so closing.