On 4/9/13, Trevor Elliott
So this did something different, but still tries to build tools like hsc2hs with the stage1 compiler. This won't really work for a target like the HaLVM, as there's no notion of a filesystem in the target environment.
I made the same observation. In cross-mode with Stage1Only many (if not all) of the compiler/ lib is built, but there is no final linking of stage2. Gabor
So, back to my original question: what's the easiest way to just generate a stage1 compiler and the libraries that it will require?
Thanks!
--trevor
On 04/08/2013 06:07 PM, Trevor Elliott wrote:
I searched on trac for bugs relating to Stage1Only, and didn't come up with anything, but a google search turned up this:
http://hackage.haskell.org/trac/ghc/ticket/7639
I'm going to try passing stage=1 in build.mk.
--trevor
On 04/08/2013 05:20 PM, Trevor Elliott wrote:
Hi Everyone,
I've been trying to produce just a stage1 compiler by setting Stage1Only in my mk/build.mk. What I've been discovering, is that the build system seems to ignore this (or I haven't set it in the right place) and trys to build a stage2 compiler and its associated tools.
What is the best way to stop the build system after stage1 + libraries has finished?
Thanks!
--trevor
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs