Discussion I've been seeing is Hadrian will not be ready for production use for 8.4. Pulling it in tree is scheduled for 8.4 mostly to make it easier to keep up to date with other changes and to make it easier to work on and test the various missing pieces: as I understand it, Hadrian can't yet deal with all of the various platform special cases, etc. that an actual release requires.
On Tue, Oct 24, 2017 at 8:02 PM, Manuel M T Chakravarty < [email protected]> wrote: > Why are you saying that? > > I think, Moritz is right. Hadrian is supposed to be the build system for > 8.4. Adding new functionality for cross-compilation to the old build system > is frustrating. > > Manuel > > Brandon Allbery <[email protected]>: > > On Tue, Oct 24, 2017 at 5:02 AM, Moritz Angermann < > [email protected]> wrote: > >> However, I am now again at the point where I start hacking on the build >> system, while Hadrian is imminent. And this is quite depressing >> > > Realistically, while Hadrian going into the tree may be imminent, as I > understand it Hadrian becoming the primary build system --- or even a > viable alternative build system --- is not. It's more of a repo logistics > speed bump. Just let it go for now. > > -- > brandon s allbery kf8nh sine nomine > associates > [email protected] > [email protected] > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > > -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
