
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 at 9:47 AM, Carter Schonwald < carter.schonwald@gmail.com> wrote:
@john, what version of cabal-install were you using? (i realize you're probably using the right one, but worth asking :) )
On Fri, Apr 25, 2014 at 12:25 PM, John Lato
wrote: On Apr 25, 2014 5:36 AM, "Bertram Felgenhauer" < bertram.felgenhauer@googlemail.com> wrote:
John Lato wrote:
I'd like to compile ghc-7.8.2 with DynamicGhcPrograms disabled (on
64-bit
linux). I downloaded the source tarball, added
DYNAMIC_GHC_PROGRAMS = NO
I've had success with setting both
DYNAMIC_BY_DEFAULT = NO DYNAMIC_GHC_PROGRAMS = NO
and removing the 'dyn' way altogether from GhcLibWays by setting GhcLibWays = v explicitely. I expect that the latter is optional; my goal was only to speed up the build.
(The lines were copied from the perf-cross settings.)
I tried disabling dynamicByDefault also, but that didn't help. It may be a problem with lib ways though, I'll try that.
Thanks, John
Cheers,
Bertram _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users