Simon Peyton Jones via ghc-devs writes:
> The Windows build is broken again. Here's the tail of the log
>
Yes, I opened a ticket (#13375) about this earlier. Running,
"C:/msys64/home/ben/ghc/inplace/bin/ghc-pkg.exe" recache
is sufficient to work around the issue it
This last email was the first one I’ve received from you.
From: Ben Gamari
Sent: Tuesday, March 7, 2017 18:50
To: Phyx; David Macek; simo...@microsoft.com; ghc-devs@haskell.org
Subject: Re: Windows build broken again
Phyx <loneti...@gmail.com> writes:
> https://ghc.haskell.org/trac/g
Phyx writes:
> https://ghc.haskell.org/trac/ghc/ticket/13375
>
Are people not receiving my messages pointing out this ticket? I've
mentioned it twice now but I get the impression that these messages
aren't being seen.
Cheers,
- Ben
signature.asc
Description: PGP
Simon Peyton Jones via ghc-devs writes:
> Windows build still broken. Please please could someone fix?
> It's something to do with the testsuite Python script
This is #13375. I have a fix in D3289. It's currently validating.
Cheers,
- Ben
signature.asc
Description:
https://ghc.haskell.org/trac/ghc/ticket/13375
On Tue, 7 Mar 2017, 08:05 David Macek, wrote:
> On 4. 3. 2017 22:01, Simon Peyton Jones via ghc-devs wrote:
> > Exception: stderr from command:
> ['"/c/code/HEAD/inplace/bin/ghc-pkg.exe"', 'dump']
>
> Pinpointing the
On 4. 3. 2017 22:01, Simon Peyton Jones via ghc-devs wrote:
> Exception: stderr from command: ['"/c/code/HEAD/inplace/bin/ghc-pkg.exe"',
> 'dump']
Pinpointing the failure. I guess `ghc-pkg dump` is not supposed to write to
stderr, but it does. Unfortunately, the test driver doesn't seem to tell
Windows build still broken. Please please could someone fix?
It's something to do with the testsuite Python script
Thanks
Simo[n
From: Simon Peyton Jones
Sent: 04 March 2017 21:01
To: ghc-devs@haskell.org
Subject: Windows build broken again
The Windows build is broken again. Here's the tail of
Simon Peyton Jones via ghc-devs writes:
> Sigh. The Simon PJ Windows Buildbot reports
>
Yes, my apologies for this one. I'm currently in the process of getting
this one fixed in D2700. Unfortunately my own Windows machine is having
hardware issues so I progress has been a
Simon Peyton Jones via ghc-devs wrote:
> In file included from rts\CheckUnload.c:16:0: error:
>
>
>
> rts\LinkerInternals.h:284:15: error:
>
> error: unknown type name 'UChar'
>
> STATIC_INLINE UChar *
There's a patch up on Phab that should fix that:
]
| Sent: 01 December 2014 08:37
| To: Simon Peyton Jones
| Subject: Re: Windows build broken again: urgent
|
| On 2014-12-01 at 09:31:51 +0100, Simon Peyton Jones wrote:
| Alas. Alack. The Windows build is broken again.
| This time it's pretty fundamental: the stage2 compiler seg-faults
Hello Simon,
On 2014-12-01 at 09:38:37 +0100, Simon Peyton Jones wrote:
| Just a hunch... could it have been broken by one of the recent linker-
| related patches since Nov 24th?
That seems very plausible, yes. But still there's the question of
what to do about it.
a) Empirically: Try
In general I think a good course of action when this happens is:
* Use git bisect to find the offending commit. This works now because we
moved to submodules.
* Revert the commit.
* Push the patch to master and notify the author.
This style of early rollback will become more important as we grow
To: Herbert Valerio Riedel
Cc: ghc-devs@haskell.org; Simon Marlow; Simon Peyton Jones
Subject: Re: Windows build broken again: urgent
In general I think a good course of action when this happens is:
* Use git bisect to find the offending commit. This works now because we moved
to submodules
it
for me.
Herbert suggested some commits to revert. I’ll try that first
*From:* Johan Tibell [mailto:johan.tib...@gmail.com]
*Sent:* 01 December 2014 09:45
*To:* Herbert Valerio Riedel
*Cc:* ghc-devs@haskell.org; Simon Marlow; Simon Peyton Jones
*Subject:* Re: Windows build broken again
yes it seems fine now, thanks.
Simon
From: Krzysztof Gogolewski [mailto:krz.gogolew...@gmail.com]
Sent: 03 October 2014 19:05
To: Herbert Valerio Riedel
Cc: Simon Peyton Jones; ghc-devs@haskell.org
Subject: Re: Windows build broken (again)
Python 3 is a likely culprit (though I couldn't confirm
Perhaps, yes, it is Python 3. I don't know. Could someone revert to make it
work again, please?
Simon
From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Simon Peyton
Jones
Sent: 02 October 2014 21:40
To: ghc-devs@haskell.org
Subject: Windows build broken (again)
Sigh. The
On 2014-10-03 at 17:29:31 +0200, Simon Peyton Jones wrote:
Perhaps, yes, it is Python 3. I don't know. Could someone revert to
make it work again, please?
Fyi, I can't reproduce this specific problem on Cygwin at least (I don't
have any working pure Msys2 environment yet (still working on it),
Python 3 is a likely culprit (though I couldn't confirm it), so I reverted
it. Does it work now?
On Fri, Oct 3, 2014 at 5:51 PM, Herbert Valerio Riedel hvrie...@gmail.com
wrote:
On 2014-10-03 at 17:29:31 +0200, Simon Peyton Jones wrote:
Perhaps, yes, it is Python 3. I don't know. Could
We need to get a windows build not up for phabricator that stops breaking
changes from getting submitted.
On Oct 2, 2014 10:40 PM, Simon Peyton Jones simo...@microsoft.com wrote:
Sigh. The testsuite fails utterly on Windows, with thousands of
identical errors
= tc012(normal) 3039 of
On Thu, Oct 2, 2014 at 4:39 PM, Simon Peyton Jones simo...@microsoft.com
wrote:
Presumably this is some kind of Windows escape-character problem. But it
has worked fine for years, so what is going on?
At a guess, something that was using / is now using \ and getting eaten by
the shell. Or
Thanks Niklas - this was an utter failure on my part. I'm not even
sure how this slipped in, but it was definitely my fault. Fixed in
6640635e6e2654f0acd8f10e0d02a8bd1c8296ff
On Tue, Jul 29, 2014 at 8:53 PM, Niklas Larsson metanik...@gmail.com wrote:
Hi!
Seems like it is the detabbing in
21 matches
Mail list logo