On 14/09/2010 11:50, Simon Peyton-Jones wrote:
This is serious: can't build GHC on MacOS.

Failing when building the .o file for GHCi.  Looks like #3260.

Short term hacks:
   a) remove codegens for all except the actual target arch
   b) compile with -fPIC
   c) reordering modules in .cabal?
   d) use two .o files?

Ben will try (a), (b).

Also, I think we plan to ship a 64-bit Mac version of 7.0.1, so that would fix it too (though not for OS X 10.5 users).

Cheers,
        SImon


Medium term: GHC 7.2: dynamic linking by default, and use system linker


Simon


| -----Original Message-----
| From: [email protected] [mailto:[email protected]] On
| Behalf Of Manuel M T Chakravarty
| Sent: 14 September 2010 02:53
| To: Ben Lippmeier
| Cc: cvs-ghc
| Subject: Re: i386/OSX build broken
|
| Another reason to move away from DIY dynamic linking and start using proper
| dynamic libraries for GHCi et al.
|
| Manuel
|
| Ben Lippmeier:
|>  It looks like Simon's mega-patch pushed us over the limit:
|>
|>  "/usr/bin/ld" -r -o compiler/stage2/build/HSghc-6.13.20100913.o
| compiler/stage2/build/AsmCodeGen.o compiler/stage2/build/TargetReg.o
| compiler/stage2/build/NCGMonad.o compiler/stage2/build/Instruction.o
| compiler/stage2/build/Size.o .........
|>  compiler/stage2/build/parser/cutils.o compiler/stage2/build/utils/md5.o
| `/usr/bin/find compiler/stage2/build -name "*_stub.o" -print`
|>  ld: scattered reloc r_address too large for inferred architecture i386
|>  make[1]: *** [compiler/stage2/build/HSghc-6.13.20100913.o] Error 1
|>
|>
|>  Related:
|>  http://hackage.haskell.org/trac/ghc/ticket/3260
|>
|>  Ben.
|
| _______________________________________________
| Cvs-ghc mailing list
| [email protected]
| http://www.haskell.org/mailman/listinfo/cvs-ghc

_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to