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, the instructions should really say that 'cvs update -dP' is only to be done in each project subdirectory. You still need to 'cvs update' at the top-level. CVS doesn't really support the structure of our source tree very well. Cheers, Simon
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 repository layout would be _flat_, like this: /cvs --+ | +-- CVSROOT | +-- fptools | +-- ghc | +-- libraries | +-- hslibs | +-- green-card [...] You could check-out the sources the same way the instructions describe it now, but an update wouldn't pull in other top-level directories. Furthermore, the entries | ghc fptools/ghc | hslibs fptools/hslibs | haddock fptools/haddock | haggis fptools/haggis | happy fptools/happy | [...] in CVSROOT/modules would be unnecessary. Instead, you could provide short cuts to check-out individual projects. For example: | ghc fptools &ghc &libraries &hslibs | green-card fptools &green-card I have been using this layout in some projects of my own, when I want to re-use separate projects as part of a bigger one and it works just fine this way. Peter
participants (2)
-
Peter Simons -
Simon Marlow