I don't believe I made this commit, or the ones around it. Mysterious; I hope
I'm not being impersonated!
Simon
From: nore...@phabricator.haskell.org [mailto:nore...@phabricator.haskell.org]
Sent: 08 July 2016 20:43
To: Simon Peyton Jones
Subject: [Diffusion]
Hi Simon,
For these tests it shouldn’t matter much so I guess I can change them.
The Windows Build guide does ask to put /mingw64/bin/ on your path.
The reason I tend not to want to use GHC to compile my c files for the tests is
that GHC doesn’t just pass the commands along to gcc.
It adds to
No, this is a Phabricator bug due to some changes in how commit imports are
handled. I just upgraded earlier; I'm tracking it down now.
At minimum, I'll find a way to turn off the email spam.
On Fri, Jul 8, 2016 at 2:46 PM, Simon Peyton Jones via ghc-devs <
ghc-devs@haskell.org> wrote:
> I
I've completed a successful build on my Surface Book! Thank you.
One last glitch. I'm getting the validate failure bellow.
No other test requires gcc in my path. GHC itself carefully navigates to its
own private gcc. Do we really want this family of tests (half a dozen
variants of T11223)
David,
Yes, that cleared all those warnings. I have no idea why it works for you but
not for me. But I'm rolling, thank you.
Simon
| -Original Message-
| From: David Macek [mailto:david.mace...@gmail.com]
| Sent: 30 June 2016 13:54
| To: Simon Peyton Jones ;