…
.section .eh_frame,"a",@progbits
Simon
From: Phyx [mailto:loneti...@gmail.com]
Sent: 09 March 2017 16:38
To: Simon Peyton Jones <simo...@microsoft.com>; ghc-devs@haskell.org
Subject: Re: Windows build failing in a new way
Hi Simon,
As of this morning the Windows build was wor
Ben Gamari writes:
> loneti...@gmail.com writes:
>
>> Ah great,
>>
>> Triples again.. I still wonder why it is suddenly an issue. We haven’t
>> touched the .m4 file in a while and no one changed libffi either
>> right? This is just like last time the normalization bit us.
loneti...@gmail.com writes:
> Ah great,
>
> Triples again.. I still wonder why it is suddenly an issue. We haven’t
> touched the .m4 file in a while and no one changed libffi either
> right? This is just like last time the normalization bit us. Causing
> days of broken builds on different targets
they were interested in.
Why do we do the normalization? It doesn’t seem to give us any benefits at
all.. Maybe we should stop doing it after the branch for 8.4?
From: Ben Gamari
Sent: Thursday, March 9, 2017 18:51
To: Phyx; Simon Peyton Jones; ghc-devs@haskell.org
Subject: Re: Windows build failing
Phyx writes:
> My CI server is also reproducing it while I also haven't been able to
> locally. Weird indeed.
>
Ahhh, I just noticed that Reid stumbled upon the culprit yesterday. See
[1].
Cheers,
- Ben
[1] https://phabricator.haskell.org/rGHCe901ed1c5d66
signature.asc
My CI server is also reproducing it while I also haven't been able to
locally. Weird indeed.
On Thu, 9 Mar 2017, 17:36 Ben Gamari, wrote:
> Simon Peyton Jones via ghc-devs writes:
>
> > My windows build is more broken than usual. I can't even build
Simon Peyton Jones via ghc-devs writes:
> My windows build is more broken than usual. I can't even build a GHC.
> Please, could someone fix this? I'm getting desperate.
This is very odd; Harbormaster is also seeing it but I've been unable to
reproduce locally. It seems
Checking again, I think something else is wrong I'll have to check later.
Sorry, but that commit above is still good. If you are really stuck use
that one.
Tamar
On Thu, 9 Mar 2017, 17:11 Phyx, wrote:
> That said, running the build on HEAD it seems that the template
That said, running the build on HEAD it seems that the template haskell
stuff committed today has broken the build again. I'd suggest checking out
the commit in my previous email which is just a few hours old. And cleaning
ghc-tarballs. As the error you seem to be getting is local.
On Thu, 9 Mar
Hi Simon,
As of this morning the Windows build was working fine
https://github.com/Mistuke/GhcWindowsBuild/commit/aa6906b2535224721d8b049cee3edcd938c3e951
those are my nightly logs for last night at commit a02b80f
That error seems to be coming from gcc and not ghc. We did update the crt
and
10 matches
Mail list logo