using a stage1 as a compiler for a later ghc?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm on a system with main ghc = 6.4.2. I've built a ghc 6.6 stage1. Is there any problem using that ghc-inplace as a compiler for GHC HEAD? (which is done e.g. by ./configure - --with-ghc=/home/isaac/hardly-mine-at-all/build/ghc-6.6/compiler/stage1/ghc-inplace ?) (which I want to do because, theoretically 6.6 should be faster here, since it supports -fasm unlike the ubuntu-edgy-powerpc-ghc-6.4.2, and also considering how my gcc likes to crash randomly a few times during anything as extensive as compiling ghc...) Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5LXeHgcxvIWYTTURAoo2AKDHUAo+7759LwBbXh5cP7zklMfKkgCdGoK9 ZQvjhkVTVUt512kpMPquDzc= =zn7+ -----END PGP SIGNATURE-----
Isaac Dupree wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm on a system with main ghc = 6.4.2. I've built a ghc 6.6 stage1. Is there any problem using that ghc-inplace as a compiler for GHC HEAD? (which is done e.g. by ./configure - --with-ghc=/home/isaac/hardly-mine-at-all/build/ghc-6.6/compiler/stage1/ghc-inplace ?)
(which I want to do because, theoretically 6.6 should be faster here, since it supports -fasm unlike the ubuntu-edgy-powerpc-ghc-6.4.2, and also considering how my gcc likes to crash randomly a few times during anything as extensive as compiling ghc...)
Sure, that should work. Cheers, Simon
participants (2)
-
Isaac Dupree -
Simon Marlow