Build description = 6.6 branch on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/ghc/nightly/STABLE-cam-02-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-6.6-cam-02-unx
Nightly build started on cam-02-unx at Thu Mar 15 19:00:01 GMT 2007.
On Thu, Mar 15, 2007 at 06:21:11PM +0100, Sven Panne wrote:
>
> IIRC, GHC has a slightly modified hsc2hs copy in its source tree. What were
> the reasons for this duplication of
> http://darcs.haskell.org:/home/darcs/hsc2hs? Shall we remove the hsc2hs from
> GHC's source tree and make hsc2hs a
On Thu, Mar 15, 2007 at 07:46:09PM +0100, Sven Panne wrote:
>
> BTW, the toplevel directory of darcs.haskell.org needs some serious cleanup,
There are plans[0] to get a "community server" where anyone can come
along and get a project hosted in darcs. The easiest way to do this
cleanup is probabl
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/ghc/nightly/HEAD-cam-02-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Thu Mar 15 19:30:01 GMT 2007.
checki
While we are at the topic: Is there a deep reason why the cpphs repo is on
www.cs.york.ac.uk and not on darcs.haskell.org? I would like to add a .spec
file etc. to make it a standalone tool, but I can't commit currently. :-(
BTW, the toplevel directory of darcs.haskell.org needs some serious cle
On Thursday 15 March 2007 17:57, Malcolm Wallace wrote:
> The only reason ghc does not ship by default with cpphs is ideological -
> the latter is GPL licensed. Of course, 3rd-party packagers (RPM,
> debian, etc) have the liberty to include cpphs anyway, and modify ghc's
> driver script accordingl
Sven Panne <[EMAIL PROTECTED]> wrote:
>they come with different sets of tools:
>
> GHC: hsc2hs
> Hugs: hsc2hs, cpphs
> nhc: cpphs
The only reason ghc does not ship by default with cpphs is ideological -
the latter is GPL licensed. Of course, 3rd-party pack
On Thursday 15 March 2007 17:43, Malcolm Wallace wrote:
> nhc98 does actually ship with hsc2hs, but it currently gets used only
> during building. It is not installed, in order to avoid conflict with
> the ghc-shipped tool of the same name.
If it's installed as hsc2hs-nhc98, then it's OK. I'll ha
Sven Panne <[EMAIL PROTECTED]> wrote:
>Alas, this doesn't work well with the Haskell
>implementations yet, because they come with different sets of
>tools (in addition to runFOO):
>
> GHC: hsc2hs
> Hugs: hsc2hs, cpphs
> nhc: cpphs
nhc98 does
Thu Mar 15 08:28:23 PDT 2007 [EMAIL PROTECTED]
* Use update-alternatives for handling generic tool names
ATTENTION: Packagers should read the following stuff carefully!
GHC, Hugs and nhc come with various tools like runhaskell or hsc2hs. On the
one hand this is quite handy, avoiding
Thu Mar 15 07:28:12 PDT 2007 [EMAIL PROTECTED]
* Make the type-defaulting in GHCi use () as the first default type
See Trac #1200
This is a somewhat experimental fix. I'm not sure we want it in 6.6.1
The idea is explained in Note [Default unitTy] in TcSimplify. In
interative m
From: GHC Build Reports <[EMAIL PROTECTED]>
To: cvs-ghc@haskell.org
Subject: [nightly] 15-Mar-2007 build of of 6.6 branch on i386-unknown-mingw32
(bling)
Build description = of 6.6 branch on i386-unknown-mingw32 (bling)
Build location= /fptools/builds/STABLE
Build config file = /fptools/buil
Thu Mar 15 05:24:57 PDT 2007 [EMAIL PROTECTED]
* Added support for parallel builds
With this patch, one can define the degree of build parallelism via a 'jobs'
rpm variable. A comfortable way to use this is having a ~/.rpmmacros file with
a line like:
%jobs 2
Alternatively,
From: GHC Build Reports <[EMAIL PROTECTED]>
To: cvs-ghc@haskell.org
Subject: [nightly] 14-Mar-2007 build of of HEAD on i386-unknown-mingw32 (bling)
Build description = of HEAD on i386-unknown-mingw32 (bling)
Build location= /fptools/builds/HEAD
Build config file = /fptools/builds/ghc-nightly/
14 matches
Mail list logo
