Deborah Goldsmith wrote:
On May 23, 2007, at 2:08 AM, Simon Marlow wrote:
Deborah Goldsmith wrote:
On May 22, 2007, at 1:59 AM, Christian Maeder wrote:
What are you trying to achieve? Did you compile parts with ghc-6.6 and
ghc-6.6.1? (That may explain the crash.)
If you have installed my binary distribution you don't need to compile
the sources anymore (except for the sake of testing).
This is purely for the sake of testing. As the subject indicates, I'm
trying to build GHC from source on 10.5. I've built earlier versions
successfully on 10.4.
I did do a "make clean" between attempts, but I will try throwing the
source directory away and re-extracting from the tar archive next.
One possibility is that if you compiled GHC via C (I believe this is
still the default in 6.6.1), then changes in the gcc shipped with 10.5
might be causing problems. You might get further by adding
SRC_HC_OPTS = -O -fasm
GhcStage1HcOpts = -O -fasm
GhcStage2HcOpts = -O -fasm
GhcLibHcOpts = -O -fasm
to your mk/build.mk. This might fix your build, but you'll still be
left with some incompatibility between GHC and the gcc in 10.5. You
already encountered one such problem, when using -split-objs, right?
If you get a successful build it should be easier to debug this.
I already have a usable build -- the 6.6.1 binary release that Christian
put together works fine on 10.5.
Actually there appears to be a problem with that 6.6.1 binary release, at least
on your system. Both crashes that you described were in the stage1 compiler,
which is compiled by your installed 6.6.1. So either
(a) your installed 6.6.1 is generating bogus code (which is why I suspected a
gcc incompatibility, because that would explain why Christian doesn't
see the same crash)
(b) there's a bug in GHC which makes it segfault on OS X 10.5.
I'd say (b) is highly unlikely - GHC just a Haskell program (well, mostly), and
it therefore shouldn't segfault.
Still, you tried with -O -fasm and that didn't help. So I'm at a loss to
explain why your stage1 GHC is crashing. Probably the only way forward at this
point is to get out gdb and figure out what's going wrong.
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
