alec.theriault at gmail.com
Fri Jan 25 08:31:39 UTC 2019
Worth noting that Hadrian additionally defines a set of so-called phony targets for packages and executables, so `./hadrian/build.sh --freeze1 build/stage1/bin/ghc` can also be expressed independently from your build root as `./hadrian/build.sh --freeze1 stage2:exe:ghc-bin`.
> On Jan 25, 2019, at 12:22 AM, Matthew Pickering <matthewtpickering at gmail.com> wrote:
> `make 2` should be somewhat equivalent to `./hadrian/build.sh
> _build/stage1/bin/ghc` I think.
> The problem is with the devel2 flavour itself. Tracked by
> The `hadrian/build.sh` script uses `cabal new-build` so the
> dependencies should be shared already when possible.
> On Fri, Jan 25, 2019 at 4:07 AM Richard Eisenberg <rae at cs.brynmawr.edu> wrote:
>> In the "devel2" flavor, I also seem to have built Haddock. `make` didn't do this with devel2, and I'd prefer Hadrian didn't, too.
>> Maybe I'm not really on the devel2 flavor?
>>> On Jan 24, 2019, at 11:02 PM, Richard Eisenberg <rae at cs.brynmawr.edu> wrote:
>>> As suggested, I'm trying out Hadrian. I have a few questions.
>>> - After building GHC the first time, I often go into the /ghc directory and then do `make 2` to build just the stage-2 compiler. Is that now the same as `build --freeze1`? It would seem not (I haven't tested), because running `make 2` builds only the compiler, not the libraries. Can this workflow be replicated in Hadrian?
>>> - I have `userDefaultFlavour = "devel2"` in my hadrian/UserSettings.hs file. But I see build artifacts during compilation of stage-2 that have dyn_o and p_o extensions. I don't want these. Have I done something wrong? Or are these artifacts now necessary?
>>> - I have quite a few ghc directories. What are the dependencies of Hadrian so that I can install these into my global package database and avoiding rebuilding them for each ghc tree? (Please don't tell me that the global package database is bad for my health. I know that, and I know why, but it's still terribly convenient, and I'm happy to pay the occasional price for that convenience.)
>>> I'm sure I'll have more questions.
>>> ghc-devs mailing list
>>> ghc-devs at haskell.org
>> ghc-devs mailing list
>> ghc-devs at haskell.org
> ghc-devs mailing list
> ghc-devs at haskell.org
More information about the ghc-devs