I ran into a similar(?) problem a while ago. "make maintainer-clean" does not necessarily remove every generated file. See for example
https://mail.haskell.org/pipermail/ghc-devs/2019-August/018049.html Since then I only use git clean -dfxq && git submodule foreach git clean -dfxq which worked reliably for me (beware that this removes any untracked file). Maybe this helps? Cheers, Stefan On Tue, Jan 28, 2020 at 10:41:33AM +0000, Simon Peyton Jones via ghc-devs wrote: > I did "sh validate --legacy" which uses "make maintainer-clean". > > I'll try again to double check. Is there any particular file I should remove? > > Simon > > | -----Original Message----- > | From: Ben Gamari <b...@smart-cactus.org> > | Sent: 27 January 2020 18:59 > | To: Simon Peyton Jones <simo...@microsoft.com>; ghc-devs <ghc- > | d...@haskell.org> > | Subject: RE: stage2 build fails > | > | Simon Peyton Jones <simo...@microsoft.com> writes: > | > | > | Indeed it would be nice to know which compiler you are using to > | > | bootstrap. I suspect Sylvain is correct that the alternative can be > | > | removed but first I would like to understand why this is arising only > | > | now. > | > > | > I'm using 8.6.4 as my bootstrap compiler. But this message occurs only > | when compiling the *stage2* compiler with the *stage1* compiler. At that > | moment the bootstrap compiler is irrelevant. > | > > | > It's as if the build system doesn't know that the stage1 compiler is >= > | 8.10 > | > > | Hmm, interesting. Has this tree been cleaned in the last month or two? > | I suspect that this may have something to do with the changes to the > | GHC_STAGE macro that were merged a while back (perhaps a stale header > | file?). > | > | Cheers, > | > | - Ben > > _______________________________________________ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs