Building GHC on NetBSD/amd64

[Simon Marlow]

On 29/07/2012 07:41, iquiw wrote:
> I am trying to build GHC on NetBSD/amd64.
>
> First, I built GHC-6.12.3 by porting from OpenBSD/amd64.
> After that, trying to build several versions (6.12.3, 7.0.4, 7.4.2) of
> GHC by the stage2 compiler.
>
> Build itself succeeded and compiling by the ghc seems no problem so far.
> However, ghci (all versions) crashes always by segmentation fault.
>
> ---------------------------------------------------------------------
> $ ghci
> GHCi, version 7.4.2: http://www.haskell.org/ghc/  :? for help
> Loading package ghc-prim ... linking ... done.
> Loading package integer-gmp ... linking ... done.
> Loading package base ... linking ... done.
> zsh: segmentation fault (core dumped)  /usr/local/ghc-7.4.2/bin/ghci
> ---------------------------------------------------------------------
>
> backtrace by gdb shows only "s2xW_info ()".
>
> ktrace (kernel trace) output is as follows.
> ---------------------------------------------------------------------
>    4494      1 ghc      CALL  __sigprocmask14(3,0x7f7fffff49e0,0)
>    4494      1 ghc      RET   __sigprocmask14 0
>    4494      1 ghc      CALL  _lwp_self
>    4494      1 ghc      RET   _lwp_self 1
>    4494      1 ghc      CALL  __sigprocmask14(1,0x7f7fffff4970,0x7f7fffff49e0)
>    4494      1 ghc      RET   __sigprocmask14 0
>    4494      1 ghc      CALL  __sigprocmask14(3,0x7f7fffff49e0,0)
>    4494      1 ghc      RET   __sigprocmask14 0
>    4494      1 ghc      CALL  issetugid
>    4494      1 ghc      RET   issetugid 0
>    4494      1 ghc      PSIG  SIGSEGV SIG_DFL: code=SEGV_MAPERR,
> addr=0xfffffffff610bfa5, trap=6)
>    4494      2 ghc      RET   __kevent50 -1 errno 4 Interrupted system call
>    4494      3 ghc      RET   ___lwp_park50 -1 errno 4 Interrupted system call
>    4494      1 ghc      NAMI  "ghc.core"
> ---------------------------------------------------------------------
>
>
> What should I check next?

I expect the dynamic linker needs something specific NetBSD/amd64, but 
it's hard to tell exactly what.  Someone needs to debug the failure and 
analyse the problem.

Cheers,
	Simon