2015-06-15 23:39 GMT+02:00 Páli Gábor János :
> The best result I was able to achive is that I passed the -P
> 'latex.unicode.use=1' flag to dblatex so it could build the PS file.
So, would you mind if I added this flag for dblatex, so it would at
least unbreak the build for me? That is, consider
On a fresh build of the 7.10 branch, I get five validate failures on Linux.
They are below. Is this only me?
Simon
Unexpected failures:
driver T8959a [bad stderr] (normal)
th T10279 [stderr mismatch] (normal)
typecheck/should_fail T10534 [stderr misma
There is a bit of a knee-jerk reaction that we should go to something
simpler than Monad as a superclass constraint for MonadFail, but I think
most of those reasons fall apart or at least lose much of their weight upon
deeper inspection.
Ultimately, I'm a not concerned about interactions between A
On Jun 17, 2015, at 8:00 AM, Simon Peyton Jones wrote:
> On a fresh build of the 7.10 branch, I get five validate failures on Linux.
> They are below. Is this only me?
>
>typecheck/should_fail T10534 [stderr mismatch] (normal)
>
>
That's probably my fault. As long as the file doesn't
OK I've pushed that change.
S
From: Richard Eisenberg [mailto:e...@cis.upenn.edu]
Sent: 17 June 2015 14:42
To: Simon Peyton Jones
Cc: ghc-devs@haskell.org
Subject: Re: Validate failures on 7.10 branch
On Jun 17, 2015, at 8:00 AM, Simon Peyton Jones
mailto:simo...@microsoft.com>> wrote:
On a
So it appears the `Missing` item is correct, but it has been given the
wrong SrcSpan. Originally it was a `noLoc`.
I think I will just advance the column by one, then it is actually correct,
and the annotation lookup will only succeed for the first one, so it will
all just work.
On Wed, Jun 17, 2
Thomas
| Update submodule process to master
|
| This allows a warning free build on Windows, and thus an error free
| validate.
I was excited about this, because GHC has not validated on Windows for ages and
ages.
But I get the following failures, with HEAD, on 32-bit Windows.
I c
