On Tue, 2008-08-19 at 15:33 +0100, Ian Lynagh wrote:
> > Hmm. We want a flag that isn't subject to Cabal's automatic resolution.
> > Duncan, is there any way to do what we want here?
>
> If not, then perhaps adding "manually-en/disabled-only" flags to Cabal
> is the way to go. This would actual
On Tue, 2008-08-19 at 15:05 +0100, Simon Marlow wrote:
> >>> However, haddock would still have to support ghc-paths for standalone
> >>> builds. Also, I think that in a GHC tree we'd still have to pointlessly
> >>> link against ghc-paths, as I can't see a simple way to avoid it.
> >> Can't this be
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 Tue Aug 19 18:02:05 BST 2008.
checking out
I just made this binary available from the darcs download page. Here's a link:
http://www.haskell.org/~simonmar/darcs-2.0.2+75.zip
This is built with curl 7.18.2 and has pipelining enabled.
Cheers,
Simon
Thanks, Simon!
I've unpacked the 2.0.0 (with cygwin) package as a basis,
but in there
1 updating ghc-paths and notifying existing clients
2 making (some) ghc api clients less dependent on a single ghcversion
dynamic linking will solve (1), but at this stage I don't think we have
time to get dynamic linking fully working and in the binary distributions
for 6.10.1. We might
>However, haddock would still have to support ghc-paths for standalone
>builds. Also, I think that in a GHC tree we'd still have to pointlessly
>link against ghc-paths, as I can't see a simple way to avoid it.
Can't this be a conditional dependency?
If you have
Flag ghcPaths
if flag(ghc
I just made this binary available from the darcs download page. Here's a link:
http://www.haskell.org/~simonmar/darcs-2.0.2+75.zip
This is built with curl 7.18.2 and has pipelining enabled.
Cheers,
Simon
Simon Marlow wrote:
The attached patches make darcs build on Windows for me using
On Tue, Aug 19, 2008 at 03:05:48PM +0100, Simon Marlow wrote:
>
> I just meant that Haddock already uses Paths_haddock to get the location of
> its own support files,
Oh, I see. Right, so as long as we give relative paths for everything
that'll work for Windows bindists, but we'll need to fix th
The attached patches make darcs build on Windows for me using GHC 6.8.3. I
ran 'make test' and most tests passed, except
TESTS FAILED!
pull.sh
which is much better than I've seen before.
The threadWaitRead issue is even more subtle than I realised. In fact
darcs does respond to ^C,
Ian Lynagh wrote:
On Windows we'll need to use the usual trick for finding the path relative
to the binary location, but that's standard stuff, and Haddock does it
already
Does it? I'm looking at the http://code.haskell.org/haddock/ repo, and
as far as I can see haddock's getGhcLibDir just lo
Tue Aug 19 03:14:37 PDT 2008 Simon Marlow <[EMAIL PROTECTED]>
* set $(BOOTSTRAPPING_PACKAGE_CONF_HC_OPTS) automatically based on $(HC)
This fixes nofib
M ./mk/config.mk.in -2 +11
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080819101437-12142-d4e0e770bb99e814d628d9e70
Tue Aug 19 05:30:16 PDT 2008 [EMAIL PROTECTED]
* Fix Trac #2518: add hs-boot files as an infelicty
M ./docs/users_guide/bugs.xml -1 +15
View patch online:
http://darcs.haskell.org/ghc/_darcs/patches/20080819123016-1287e-3ba42c4beb64f5e597635acafcfb57f7b00f370d.gz
_
On Mon, Aug 18, 2008 at 09:31:35AM +0100, Simon Marlow wrote:
> Ian Lynagh wrote:
> >Sat Aug 16 12:02:22 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]>
> > * Skip num009 if fast, as it gives the wrong answer on some platforms
>
> Do we know why?
No, but I doubt it ever gave the right answer (i.e. I do
On Tue, Aug 19, 2008 at 11:26:24AM +0100, Simon Marlow wrote:
>
> seem so hard to install Haddock with GHC. We have to do the wrapper script
> business for GHC itself anyway and you already added support to Cabal for
> this, so (I imagine) it shouldn't be too hard to do this for Haddock too.
Ian Lynagh wrote:
I've been thinking about haddock 2 and GHC, and it's not clear to me
what the best way forwards is.
Haddock uses ghc-paths to work out where the GHC libdir is. This should
work fine for running haddock in the tree, but it won't work for
installing haddock as our builds are rel
Build results:
x86-64 Linux head:lost
x86 Windows head: fail (failed darcs)
x86 Windows head fast:pass pass pass fail (failed getsubrepos) pass
pass lost
fast486 head: pass
gabor head: lost
kgardas head: fail (failed
Build results:
tnaur PPC OSX stable 2: pass
tnaur x86 Linux stable: pass
x86 Windows stable: fail (failed getsubrepos)
x86 Windows stable fast: pass pass pass pass pass lost
x86-64 Linux stable: lost
Old unexpected test failures:
TyFamUndec 4 mnemosyne x86-64 Gentoo stabl
17 matches
Mail list logo
