No! Sorry for the confusion Simon, it is HEAD _PLUS_ my own commit that triggers these errors. Oh, and I should add that 'my own commit' is only in my own development repository. So, no worries!
/Dan On Fri, Aug 30, 2013 at 4:44 PM, Simon Peyton-Jones <simo...@microsoft.com>wrote: > Wait.. are you saying that with HEAD several test suite programs fail as > you describe below? If so, which? > > Simion**** > > ** ** > > *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of *Dan > Rosén > *Sent:* 30 August 2013 14:26 > *To:* David Luposchainsky > *Cc:* ghc-devs@haskell.org > *Subject:* Re: Cannot make ghc: Failed to load interface for GHC.Base**** > > ** ** > > Closed, but a note to interested readers: > > killy9999 on #ghc realized the reason why the stage1 compiler cannot be > built with this patch is related to that several test suite programs exit > with erros like this:**** > > GHC/Base.lhs:1:1:**** > > GHC internal error: 'GHC.Base.Monad' is not in scope during type > checking, but it passed the renamer**** > > tcl_env of environment: []**** > > > So the error is resolved, and now productive debugging can start.**** > > ** ** > > On Fri, Aug 30, 2013 at 2:50 PM, Dan Rosén <d...@chalmers.se> wrote:**** > > Sorry! I thought I got this build error when making HEAD, but I don't. > It builds fine. > > However, if I just cherry-pick this simple commit onto HEAD > https://github.com/danr/ghc/commit/86631ffd294af320cb9b00e1a593201af887ed72 > , > then I do get this error, which is very puzzling. I did a make > maintainer-clean in between. **** > > ** ** > > On Thu, Aug 29, 2013 at 6:05 PM, David Luposchainsky < > dluposchain...@googlemail.com> wrote:**** > > On 2013-08-29 18:03, Austin Seipp wrote: > > When was the last time you cleaned your tree? Earlier this week I made a > > breaking change to the interface file format. If you have a build from > > before then, update and incrementally rebuild, it will break.**** > > I tried all of clean, distclean and maintainer-clean, followed by the > usual build process. The issue remains.**** > > > David > > > _______________________________________________ > ghc-devs mailing list > ghc-devs@haskell.org > http://www.haskell.org/mailman/listinfo/ghc-devs**** > > ** ** > > ** ** >
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
