RE: Problems building ghc-current

> Simon Marlow writes: > > > We could just rearrange the repository in place, and > everything would > > still work, right? > > It's not quite that easy, unfortunately. If you want to retain the > files's version history (and I guess you would), then you have to move > the directories around

RE: Problems building ghc-current

> "Simon Marlow" <[EMAIL PROTECTED]> writes: > > > > /cvs --+ > > >| > > >+-- CVSROOT > > >| > > >+-- fptools > > >| > > >+-- ghc > > >| > > >+-- libraries > > >| > > >+--

Re: Problems building ghc-current

"Simon Marlow" <[EMAIL PROTECTED]> writes: > > /cvs --+ > >| > >+-- CVSROOT > >| > >+-- fptools > >| > >+-- ghc > >| > >+-- libraries > >| > >+-- hslibs > >| > >

Re: Problems building ghc-current

Simon Marlow writes: > We could just rearrange the repository in place, and everything would > still work, right? It's not quite that easy, unfortunately. If you want to retain the files's version history (and I guess you would), then you have to move the directories around in the CVS repositor

RE: Problems building ghc-current

> The problem is that >ghc<, >green-card<, >hood< et al. are > subdirectories of >fptools<, that's why >cvs update -d< retrieves them > automatically. I guess a more appropriate repository layout would be > _flat_, like this: > > /cvs --+ >| >+-- CVSROOT >

Re: Problems building ghc-current

Volker Stolz writes: > [STABLE branch] Does the »STABLE« branch contain the meta-haskell extensions already? Because this was the reason I wanted to run the CVS version in the first place. :-) Oh, and I have news: The build does not work yet, unfortunately. It fails here: | --

Re: Problems building ghc-current

In local.glasgow-haskell-users, you wrote: > | 2.4. Updating Your Source Tree > | It can be tempting to cvs update just part of a source tree to bring in > | some changes that someone else has made, or before committing your own > | changes. This is NOT RECOMMENDED! [...] > | > | So, to avoid a lot

Re: Problems building ghc-current

Simon Marlow writes: > CVS doesn't really support the structure of our source tree very > well. Actually, it does. ;-) The problem is that »ghc«, »green-card«, »hood« et al. are subdirectories of »fptools«, that's why »cvs update -d« retrieves them automatically. I guess a more appropriate rep

Re: Problems building ghc-current

Alastair Reid writes: > The attached diff (about to be committed) seems to fix the problem. It does indeed -- thank you very much for your help! One problem remains, though: When I build GHC from the top-level directory, the build process does get the order right. It tries to build »green-card/

RE: Problems building ghc-current

> I'm trying to compile the latest version of GHC from CVS. I followed > the instructions on GHC's web page and everything worked just fine. > But when I updated the sources with "cvs update -dP" as instructed, > CVS checked-out pretty much everything the CVS repository carries. Sorry about that

Re: Problems building ghc-current

> Alastair: Thanks a lot for the detailed reply! I'll take a look at the > build again; maybe I can get this problem fixed after all. The attached diff (about to be committed) seems to fix the problem. -- Alastair? gc-3.00 ? distrib/html/old_index.html ? lib/Foreign/GreenCard.p_hi ? lib/Foreign/

Re: Problems building ghc-current

Volker Stolz writes: > Where did you find those instructions? At : | 2.4. Updating Your Source Tree | | It can be tempting to cvs update just part of a source tree to bring in | some changes that someone else has made, o

Re: Problems building ghc-current

In local.glasgow-haskell-users, you wrote: > I'm trying to compile the latest version of GHC from CVS. I followed > the instructions on GHC's web page and everything worked just fine. > But when I updated the sources with "cvs update -dP" as instructed, > CVS checked-out pretty much everything the

Problems building ghc-current

Hi, I'm trying to compile the latest version of GHC from CVS. I followed the instructions on GHC's web page and everything worked just fine. But when I updated the sources with "cvs update -dP" as instructed, CVS checked-out pretty much everything the CVS repository carries. (Is that supposed to h