Simon Marlow wrote:
> I've just finished building 5.02.3 on sparc-solaris, and didn't get any
> core dumps, so there must be something different about your setup. What
> version of
> gcc are you using? What version of GHC are you bootstrapping with?
$ gcc -v
Reading specs from .../gcc-lib/sparc-sun-solaris2.5.1/2.95.2/specs
gcc version 2.95.2 19991024 (release)
For GHC I tried 5.02.1 and 5.02.2 binaries for solaris. The core dump due
to bus error occurs when building from 5.02.2 AND 5.02.3 sources. It did
not occur when building from 5.02.1 sources and setting
GhcRtsHcOpts = -optc-DDEBUG -optc-g -keep-hc-file
GhcRtsCcOpts = -g
in mk/build.mk. I don't know whether the default build components have
changed from 5.02.1 to 5.02.2, and Monad.p_o was never built (I have no
make log from that build and had to remove the source tree to make room
for the 5.02.2 source).
I tried looking at the core dump with ddd, but it got an internal bus error
while loading the the core file. Any suggestions on what to look at to get
more insight into the root cause of this?
What's special about Monad.p_o? As part of this build, ghc-inplace was
used many times before to compile *.o's (incl Monad.o) and other *.p_o's
without problems.
> > $ echo "prefix = /home/dorr/func/haskell/installs/ghc-5.02.2"
> > >mk/build.mk
>
> Better to set prefix at configure time (i.e. ./configure --prefix=...).
Better as in simpler, or really better? After a default build works, I need
to set GhcRtsHcOpts, GhcRtsCcOpts, and potentially other parameters.
Shouldn't I just start a build.mk anyway rather then pass all of these into
./configure? Are there guidelines on when to define parameters via
./configure options versus build.mk?
> > $ cd ghc
> > $ ./configure
>
> not necessary - the top-level configure script invokes the lower ones.
>
> > $ cd rts/gmp
> > $ ./configure
>
> not necessary - this is invoked by the Makefile in ghc/rts if necessary.
Thanks for pointing this out. The instructions to run autoconf in directories
with configure.in led me to believe I need to run ./configure too. When I am
excited to get it right, the best build instructions don't help ;-).
Martin
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
