Two questions about building GHC from sources

[Moritz Angermann]

(1), I would hope so. If not, that's a bug.
(2), hadrian supports --build-root=, such that you can have different build
product trees based from one source. One of the nice features of hadrian
is, that it finally is able to separate build and source directories, there
are still the inplace files, which I believe should go. Yet, anything under
the --build-root, which defaults to _build, should be hermetic in there.
Whether or not you can just *move* those directories around is a bit
complicated, primarily because there are facilities in Cabal (the Paths
module), as well as potentially use of non ${pkgroot} prefixed package
config files, that hardcode paths. Again the Paths module from Cabal should
just be removed at some point. And missing ${pkgroot} values could be
fixed. My guess is, that we've done quite a lot of making it relocatable,
so just try to move it somewhere else and see if things break when calling
it somewhere else, they might, but if they do, it's a bug.


On Wed, Sep 22, 2021 at 3:27 PM Norman Ramsey <nr at cs.tufts.edu> wrote:

> I've got two questions about building:
>
>  1. If my bootstrap compiler changes (e.g., from 8.10.5 to 9.0.1), is
>     Hadrian smart enough to rebuild everything?  If not, how do I
>     force it to start over?
>
>  2. At the moment I'm not installing my GHC; I'm using elements
>     directly from the build tree.  If I build GHC and then move the
>     whole tree to the whole location, will everything be happy?
>     Or do I need to do something?  (Again, using Hadrian.)
>
>
> Norman
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20210922/38c7c404/attachment.html>