> it's very easy to end up in a state where `make` simply can't build, and only
> easy fix is a `make clean`
Out of sheer curiosity: in what situations does that happen for you? *If* you
are working on a
single branch, ie. you're not switching back and forth between master and your
feature
Hi Ömer,
in mk/build.mk, set:
* Stage1Only=YES
* stage=1
* BuildFlavour=devel1
Then 'cd ghc && make'. Don't run make in the toplevel directory.
After building the stage1 compiler, it does still start the process of
configuring the libraries for the stage2 compiler, but it shouldn't build
them.
> Out of sheer curiosity: in what situations does that happen for you? *If* you
> are working on a single branch, ie. you're not switching back and forth
> between master and your feature branches, this should not happen (and even if
> you switch between branches it should still be safe for most
(I know I asked this many times in IRC channel but I don't remember getting any
answers. I apologize if anyone had answered this on IRC channel and I missed)
With current build system, even if I choose "devel1" it always builds stage2
compiler too. A comment in build.mk says that it's for working
I haven't tested this, but I imagine putting `stage=1` in your build.mk or even
on the command line should work.
Richard
On Oct 19, 2015, at 4:47 PM, Ömer Sinan Ağacan wrote:
> (I know I asked this many times in IRC channel but I don't remember getting
> any
> answers.