Thanks,
Claus
- Original Message -
From: "Duncan Coutts" <[EMAIL PROTECTED]>
To: "Claus Reinke" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, August 13, 2008 1:49 PM
Subject: Re: headless on windows
On Mon, 2008-08-11 at 01:00 +0100, Claus Reinke wrote:
For my issue (build failure wit
On Wed, 2008-08-13 at 22:47 +1000, Roman Leshchinskiy wrote:
> Again, I'm not arguing against a build system written in Haskell. I'd
> just like it to be completely separated from Haskell's packaging
> system. In particular, "polluting" a package description with build
> information seems wr
On Mon, 2008-08-11 at 01:00 +0100, Claus Reinke wrote:
> For my issue (build failure with insufficient stack space for haddock
> called via cabal), it would have been sufficient if 'Setup haddock --help'
> would have pointed to 'Setup configure --haddock-option(s)' - a simple
> but useful document
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Wed Aug 13 18:02:05 BST 2008.
checking out
On Wed, Aug 13, 2008 at 5:18 AM, Claus Reinke <[EMAIL PROTECTED]> wrote:
> The earlier we start collecting _concrete_ instances of such silent
> command failures, the better.
Unfortunately, I can't remember what I was doing at the time, as this
occurred a few months ago.
On 13/08/2008, at 20:34, Simon Marlow wrote:
Roman Leshchinskiy wrote:
Of course there should be a standard build system for simple
packages. It could be part of Cabal or a separate tool (for which
Cabal could, again, act as a preprocessor).
GHC is a special case: we already need a build sy
A number of git commands are implemented as crufty shell scripts that
don't check the results of running its plumbing commands. I've been
bitten by silent command failure on a number of occasions. Just
saying.
The earlier we start collecting _concrete_ instances of such silent
command failures,
"darcs-all get; darcs-all pull -a; sh validate" instead of just the latter two.
actually, since pull might change darcs-all or packages, either of which
may change what "darcs-all get" does, that needs to be
"darcs-all pull -a; darcs-all get; sh validate"
which, since pull might change darcs-a
On Wed, 2008-08-13 at 11:34 +0100, Simon Marlow wrote:
> Cabal has two parts: some generic infrastructure, and a "simple" build
> system (under Distribution.Simple) that suffices for most packages. We
> distribute them together only because it's convenient; you don't have to
> use the simple b
OK so the problem here was a missing package base3-compat, fixed by
darcs-all get
Suggestions (of an overlapping nature).
1. All: everyone who adds a core library should email cvs-ghc with a clear
heads-up to remind us to darcs-all get. (Same process for interface file
format changes.
Ian Lynagh wrote:
On Tue, Aug 12, 2008 at 11:11:38AM +0100, Simon Marlow wrote:
I propose we do this:
- Extract the code from Cabal that generates Makefiles, and treat it as
part of the GHC build system. Rather than generating a Makefile
complete with build rules, we generate a Makefile
Roman Leshchinskiy wrote:
Of course there should be a standard build system for simple packages.
It could be part of Cabal or a separate tool (for which Cabal could,
again, act as a preprocessor).
GHC is a special case: we already need a build system for other reasons.
I agree. I just don'
Wed Aug 13 02:45:06 PDT 2008 [EMAIL PROTECTED]
* Improve error message for deprecated flags (Trac #2513)
M ./compiler/main/DynFlags.hs -3 +5
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080813094506-1287e-16c18c3fdbf9ae83dccdd000244094414d50ec22.gz
Wed Aug 13 01:28:28 PDT 2008 [EMAIL PROTECTED]
* Improve docs for orphan decls (thanks Yitzchak Gale)
M ./docs/users_guide/separate_compilation.xml -3 +4
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080813082828-1287e-bcc91823ff5e4d0ee01da4ad44eb7c663b2ceff5.gz
___
On 13/08/2008, at 17:47, Simon Marlow wrote:
Roman Leshchinskiy wrote:
On 12/08/2008, at 20:11, Simon Marlow wrote:
- Extract the code from Cabal that generates Makefiles, and treat
it as
part of the GHC build system. Rather than generating a Makefile
complete with build rules, we generat
Roman Leshchinskiy wrote:
On 12/08/2008, at 20:11, Simon Marlow wrote:
- Extract the code from Cabal that generates Makefiles, and treat it as
part of the GHC build system. Rather than generating a Makefile
complete with build rules, we generate a Makefile that just
has the package-speci
Build results:
x86-64 Linux head: lost
x86 Windows head:fail (failed bindist bindisttest boottestsuite
runtestsuite nofib.boot.0 nofib.boot.0_2 nofib.boot.0_3 nofib.boot.0_4
nofib.boot.0_5)
x86 Windows head fast: fail (failed boottestsuite runtestsuite) fail (failed
boottestsuite
Build results:
tnaur PPC OSX stable 2: pass
tnaur x86 Linux stable: pass
x86 Windows stable: fail (failed stage1)
x86 Windows stable fast: pass pass pass fail (failed darcs) pass fail (failed
getsubrepos)
x86-64 Linux stable: fail (failed stage1)
New unexpected test failures:
conc
18 matches
Mail list logo
