Hi Carter,
cabal-install-1.20.0.0, using Cabal 1.20.0.0. But this also happened IIRC
with just ghc, no libraries installed, and no cabal anywhere on the path.
In any case, thus far the worst behavior I've seen from a too-old cabal is
a compile failure, not a core dump :)
On Fri, Apr 25, 2014 a
+1 from me
I’ve been meaning to say essentially the same thing as you just did. We all
seem to concentrate on *adding* things to GHC; it’s a bit refreshing to
consider *removing* something.
Echoing Austin somewhat:
- Anyone using external core is either working with an old GHC or is kludging
Hello all,
Recently I was wondering something: is there any reason to keep
-fext-core around? In particular, it's been broken for a while at this
point, see GHC bug #5630[1]
As far as I'm aware there really aren't any users of it still around
these days, at least none working with a modern GHC. A
John Lato-2 wrote
> I'd like to compile ghc-7.8.2 with DynamicGhcPrograms disabled
Are you able to use template haskell (and qusiquoting) with this? Don't they
need dynamic libs?
--
View this message in context:
http://haskell.1045720.n5.nabble.com/how-to-compile-non-dynamic-ghc-7-8-2-tp574841
