Hi,

I'm trying to get caballized package deployment working on Mac OS X.

However, trying to build a package using runhaskell results in:


crossroads-able> runhaskell Setup.hs configure
Warning: No license-file field.
Configuring harp-0.2...
configure: searching for ghc in path.
configure: found ghc at /opt/local/bin/ghc
runhaskell: waitForProcess: interrupted (Interrupted system call)


This was trying to build the harp module in the haskell-src-exts package
(a prerequisite for hs-plugins).

I ran a ktrace on this and it appears as if the underlying GHC is segfaulting:

crossroads-able> cat k.txt
   414 ghc-6.4  RET   write 1
   414 ghc-6.4  CALL  getpid
   414 ghc-6.4  RET   getpid 414/0x19e
   414 ghc-6.4  CALL  stat(0x1b94528,0x1b944c0)
   414 ghc-6.4  NAMI  "tmp414"
   414 ghc-6.4  RET   stat -1 errno 2 No such file or directory
   414 ghc-6.4  CALL  sigprocmask(0x1,0xbfffd4d0,0xbfffd4d4)
   414 ghc-6.4  RET   sigprocmask 0
   414 ghc-6.4  CALL  sigaction(0x2,0xbfffd458,0)
   414 ghc-6.4  RET   sigaction 0
   414 ghc-6.4  CALL  sigprocmask(0x3,0xbfffd4d4,0)
   414 ghc-6.4  RET   sigprocmask 0
   414 ghc-6.4  CALL  sigprocmask(0x1,0xbfffd4d0,0xbfffd4d4)
   414 ghc-6.4  RET   sigprocmask 0
   414 ghc-6.4  CALL  sigaction(0x3,0xbfffd458,0)
   414 ghc-6.4  RET   sigaction 0
   414 ghc-6.4  CALL  sigprocmask(0x3,0xbfffd4d4,0)
   414 ghc-6.4  RET   sigprocmask 0
   414 ghc-6.4  CALL  fcntl(0,0x3,0)
   414 ghc-6.4  RET   fcntl 6
   414 ghc-6.4  CALL  fcntl(0,0x4,0x6)
   414 ghc-6.4  RET   fcntl 0
   414 ghc-6.4  CALL  ioctl(0,0x4004667a ,0xbfffd4b8)
   414 ghc-6.4  RET   ioctl 0
   414 ghc-6.4  PSIG  SIGSEGV SIG_DFL
   413 runhaskell RET   wait4 414/0x19e
   413 runhaskell CALL  write(0x2,0xbfffcf40,0xc)
   413 runhaskell GIO   fd 2 wrote 12 bytes
       "runhaskell: "
   413 runhaskell RET   write 12/0xc
   413 runhaskell CALL  write(0x2,0xbfffcfa0,0x36)
   413 runhaskell GIO   fd 2 wrote 54 bytes
       "waitForProcess: interrupted (Interrupted system call)
       "


This is a bit surprising. Any suggestions on how to track down the problem?

Best Wishes,
Greg


_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to