Thu Sep 18 06:36:36 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Generate ghc.cabal and ghc-bin.cabal with configure
This allows us to put the proper version number into them
./compiler/ghc.cabal -> ./compiler/ghc.cabal.in
./ghc/ghc-bin.cabal -> ./ghc/ghc-bin.cabal.in
; > > > John discovered (we think) that a new feature of the build system is
> > > > that all GHC's source modules must be listed by the developer in
> > > > ghc.cabal.
> > >
> > > Yes.
> >
> > Although it's not actually new; b
> > > that all GHC's source modules must be listed by the developer in
> > > ghc.cabal.
> >
> > Yes.
>
> Although it's not actually new; before you had to list all the modules
> in package.conf.in. With the old system I suspect it wouldn't go wron
On Mon, Aug 04, 2008 at 10:40:58PM +0100, Duncan Coutts wrote:
> On Mon, 2008-08-04 at 16:33 +0100, Simon Peyton-Jones wrote:
> >
> > John discovered (we think) that a new feature of the build system is
> > that all GHC's source modules must be listed by the developer
On Mon, 2008-08-04 at 16:33 +0100, Simon Peyton-Jones wrote:
> Ian
>
> John discovered (we think) that a new feature of the build system is
> that all GHC's source modules must be listed by the developer in
> ghc.cabal.
Yes.
> Actually gets a long way without this, but t
Ian
John discovered (we think) that a new feature of the build system is that all
GHC's source modules must be listed by the developer in ghc.cabal.
Actually gets a long way without this, but there's a confusing link error later.
(The old make system would just use whatever .hs
Wed Jul 30 14:34:19 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
* Add the Exception module to ghc.cabal
M ./compiler/ghc.cabal +1
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080730213419-3fd76-3db49107581b8426b23be9ffdef46644214d6
