I've discovered that passing options to `make` doesn't necessarily work all
that well. Certain ones work great, but it's not as reliable as I might like.
That said, have you tried running the command in the ./ghc subdirectory? (Not
the top directory -- it's probably ./ghc/ghc on your
I did try that. I've found that if I run `make` in the toplevel, I can just
look at the last command it executes (which is generating all the
documentation) and copy/paste all of the huge command to rerun it. It's a
terrible solution but works well for me...
If you run it from the `ghc`
Any suggestions? I'm still stuck on this, and don't really know what to try
next.
Andrew
On Thu, Jul 10, 2014 at 9:36 PM, Andrew Gibiansky
andrew.gibian...@gmail.com wrote:
Hello,
I am trying to create my first patch, for #9294, where I want to export
some extra things from Parser along
if you wanna resuse the same source tree, the heavy hammer for doing a
rebuild is
make maintainer-clean ; make
maintainer-clean wipes alll build artifacts so its a clean tree, so
everything will be built from scratch
there might be a better way, but that sledgehammer should work
On Mon, Jul
wooops, would need to be
make maintainer-clean ; perl boot ; ./configure ; make
On Mon, Jul 14, 2014 at 11:07 PM, Carter Schonwald
carter.schonw...@gmail.com wrote:
if you wanna resuse the same source tree, the heavy hammer for doing a
rebuild is
make maintainer-clean ; make
Hello,
I am trying to create my first patch, for #9294, where I want to export
some extra things from Parser along with a bit of documentation. However, I
cannot figure out how to regenerate the documentation for the GHC API (not
for the libraries).
I tried running `make html stage=0 FAST=YES`