Re: Windows build broken

Andreas Klebinger writes: > Hi devs, > > it seems the windows build is broken. (Can't build stage2 locally). > > Quickest way to reproduce is a validate of master. > > It also happens on CI: https://gitlab.haskell.org/ghc/ghc/-/jobs/270248 > > I remember ben mentioning something along the lines

Windows build broken

Hi devs, it seems the windows build is broken. (Can't build stage2 locally). Quickest way to reproduce is a validate of master. It also happens on CI: https://gitlab.haskell.org/ghc/ghc/-/jobs/270248 I remember ben mentioning something along the lines of builds with "old" (8.6) boot compilers

Re: Fwd: [hadrian/windows] build broken

Shayne Fletcher via ghc-devs writes: > On Thu, May 30, 2019 at 8:32 AM Alp Mestanogullari > wrote: > >> Heh, it landed less than an hour ago. >> >> If the error persists, you'll probably want to do a clean build, by >> removing at the very least _build/stage1, even though I'd say it can't hurt

Re: Fwd: [hadrian/windows] build broken

On Thu, May 30, 2019 at 9:18 AM Alp Mestanogullari wrote: > I haven't (yet) worked on making an OS X job for Hadrian. I brought back > the Windows/Hadrian CI job with that fix, but then tried running the > testsuite, which didn't go well, see: > >

Re: Fwd: [hadrian/windows] build broken

I haven't (yet) worked on making an OS X job for Hadrian. I brought back the Windows/Hadrian CI job with that fix, but then tried running the testsuite, which didn't go well, see: https://gitlab.haskell.org/ghc/ghc/merge_requests/1035 https://gitlab.haskell.org/alp/ghc/-/jobs/87467 This

Re: Fwd: [hadrian/windows] build broken

On Thu, May 30, 2019 at 8:32 AM Alp Mestanogullari wrote: > Heh, it landed less than an hour ago. > > If the error persists, you'll probably want to do a clean build, by > removing at the very least _build/stage1, even though I'd say it can't hurt > to remove _build altogether. Along with that

Re: Fwd: [hadrian/windows] build broken

Heh, it landed less than an hour ago. If the error persists, you'll probably want to do a clean build, by removing at the very least _build/stage1, even though I'd say it can't hurt to remove _build altogether. Along with that patch, I also brought back the Windows CI job and the error did

Re: Fwd: [hadrian/windows] build broken

On Thu, May 30, 2019 at 6:55 AM Shayne Fletcher wrote: > Hi Alp, > > On Fri, May 24, 2019 at 11:34 AM Shayne Fletcher > wrote: > >> >> On Fri, May 24, 2019 at 7:33 AM Alp Mestanogullari >> wrote: >> >>> Hello Shayne, >>> >>> David and I figured out the cause of that problem, I am working on a

Re: Fwd: [hadrian/windows] build broken

Hi Alp, On Fri, May 24, 2019 at 11:34 AM Shayne Fletcher wrote: > > On Fri, May 24, 2019 at 7:33 AM Alp Mestanogullari > wrote: > >> Hello Shayne, >> >> David and I figured out the cause of that problem, I am working on a >> patch, will put it up as a (WIP) MR as soon as it's ready. >> >> >

Re: Fwd: [hadrian/windows] build broken

On Fri, May 24, 2019 at 7:33 AM Alp Mestanogullari wrote: > Hello Shayne, > > David and I figured out the cause of that problem, I am working on a > patch, will put it up as a (WIP) MR as soon as it's ready. > > Awesome! -- Shayne Fletcher Language Engineer c: +1 917 699 7763 e:

Re: Fwd: [hadrian/windows] build broken

Hello Shayne, David and I figured out the cause of that problem, I am working on a patch, will put it up as a (WIP) MR as soon as it's ready. On 24/05/2019 13:10, Shayne Fletcher via ghc-devs wrote: Hi David, On Thu, May 23, 2019 at 8:09 AM David Eichmann >

Re: Fwd: [hadrian/windows] build broken

Hi David, On Thu, May 23, 2019 at 8:09 AM David Eichmann wrote: > Ooops I've let this thread pass by me, but this is most likely due to my > latest refactoring of libffi rules in Hadrian. No need to create a new > issue, I'll just reopen #16304, and have a look at this now. > Hate to nag - any

Re: Fwd: [hadrian/windows] build broken

> > -- Forwarded message - > From: Shayne Fletcher > Date: Wed, May 22, 2019, 13:03 > Subject: Re: [hadrian/windows] build broken > To: GHC developers > > > I guess, > > On Wed, May 22, 2019 at 12:27 PM Shayne Fletcher > wrote: > >> Windows build

Re: Fwd: [hadrian/windows] build broken

e: > > No comments on this. Maybe I should raise a ticket? Anybody got an email > address to ping David on? > > -- Forwarded message - > From: Shayne Fletcher > Date: Wed, May 22, 2019, 13:03 > Subject: Re: [hadrian/windows] build broken > To: GHC deve

Re: Fwd: [hadrian/windows] build broken

* <mailto:shayne.fletc...@daml.com>> Date: Wed, May 22, 2019, 13:03 Subject: Re: [hadrian/windows] build broken To: GHC developers mailto:ghc-devs@haskell.org>> I guess, On Wed, May 22, 2019 at 12:27 PM Shayne Fletcher mailto:shayne.fletc...@daml.com>> wrote: Windows builds with

Re: Fwd: [hadrian/windows] build broken

bject: Re: [hadrian/windows] build broken To: GHC developers mailto:ghc-devs@haskell.org>> I guess, On Wed, May 22, 2019 at 12:27 PM Shayne Fletcher mailto:shayne.fletc...@daml.com>> wrote: Windows builds with hadrian are currently failing with "file does not exist a

Fwd: [hadrian/windows] build broken

No comments on this. Maybe I should raise a ticket? Anybody got an email address to ping David on? -- Forwarded message - From: Shayne Fletcher Date: Wed, May 22, 2019, 13:03 Subject: Re: [hadrian/windows] build broken To: GHC developers I guess, On Wed, May 22, 2019 at 12:27

Re: [hadrian/windows] build broken

Yes, I suspect so, even though I'll let David (cc'd) talk about this, as he's the one who's been working on this. On 22/05/2019 19:03, Shayne Fletcher via ghc-devs wrote: I guess, On Wed, May 22, 2019 at 12:27 PM Shayne Fletcher mailto:shayne.fletc...@daml.com>> wrote: Windows builds

Re: [hadrian/windows] build broken

I guess, On Wed, May 22, 2019 at 12:27 PM Shayne Fletcher wrote: > Windows builds with hadrian are currently failing with "file does not > exist and no build rule available" > `_build/stage1/libffi/build/inst/bin/libffi-6.dll`. Anybody have an ideas > on how to overcome that? > > relates to

[hadrian/windows] build broken

Windows builds with hadrian are currently failing with "file does not exist and no build rule available" `_build/stage1/libffi/build/inst/bin/libffi-6.dll`. Anybody have an ideas on how to overcome that? -- Shayne Fletcher Language Engineer c: +1 917 699 7763 e: shayne.fletc...@daml.com Digital

RE: Windows build broken -- help!

I’ve pushed the commit. Thanks Doug! From: Douglas Wilson Sent: Wednesday, February 7, 2018 23:33 To: Simon Peyton Jones Cc: ghc-devs Subject: Re: Windows build broken -- help! Hi Simon, The first patch you quoted half-fixed this. the patch here: https://phabricator.haskell.org/D4392 should

Re: Windows build broken -- help!

t; Subscribers: rwbarton, thomie, carter > > > > Differential Revision: https://phabricator.haskell.org/D4374 > > > > > > *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of *Simon > Peyton Jones via ghc-devs > *Sent:* 07 February 2018 23:1

Windows build broken -- help!

Aargh. Windows build is broken again. Log below. Help! Simon "inplace/bin/ghc-stage1.exe" -optc-fno-stack-protector -optc-Wall -optc-Werror -optc-Wall -optc-Wextra -optc-Wstrict-prototypes -optc-Wmissing-prototypes -optc-Wmissing-declarations -optc-Winline -optc-Waggregate-return

RE: Windows build broken

From: Phyx [mailto:loneti...@gmail.com] Sent: 04 October 2017 13:30 To: Simon Peyton Jones <simo...@microsoft.com>; ghc-devs@haskell.org Subject: Re: Windows build broken Hi Simon, You seem to be in an msys shell instead of a mingw-64 shell (they have different startup shortcuts). We

Re: Windows build broken

Phyx writes: > Hi Simon, > > You seem to be in an msys shell instead of a mingw-64 shell (they have > different startup shortcuts). We don't support the msys shell as we only > want to compile for native windows. > > You should use the shortcut marked mingw-64. > >

Re: Windows build broken

Hi Simon, You seem to be in an msys shell instead of a mingw-64 shell (they have different startup shortcuts). We don't support the msys shell as we only want to compile for native windows. You should use the shortcut marked mingw-64. Alternatively to get you going in aclocal.m4 remove line

Windows build broken

My Windows build is broken again. With a clean checkout, I get "" Target platform inferred as: x86_64-unknown-mingw32 Unknown OS msys How can I get past this? Full log below. Simon make[1]: Leaving directory '/c/code/HEAD/testsuite' ['libraries/array/', 'libraries/base/',

Re: Windows build broken again

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

RE: Windows build broken again

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

Re: Windows build broken again

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

RE: Windows build broken again

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:

Re: Windows build broken again

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

Re: Windows build broken again

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

RE: Windows build broken again

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

Windows build broken again

The Windows build is broken again. Here's the tail of the log It would be good if we could stop this happening Simon == End post-build package check make: Entering directory '/c/code/HEAD/testsuite/tests' WARNING: cache is out of date:

RE: Windows build broken

ll.org Subject: Windows build broken Windows build is broken again.  Might someone fix? Simon   "inplace/bin/ghc-stage1.exe" -optc-fno-stack-protector -optc-Wall -optc-Werror -optc-Wall -optc-Wextra -optc-Wstrict-prototypes -optc-Wmissing-prototypes -optc-Wmissing-declarations -op

Windows build broken

Windows build is broken again. Might someone fix? Simon "inplace/bin/ghc-stage1.exe" -optc-fno-stack-protector -optc-Wall -optc-Werror -optc-Wall -optc-Wextra -optc-Wstrict-prototypes -optc-Wmissing-prototypes -optc-Wmissing-declarations -optc-Winline -optc-Waggregate-return

Re: Windows build broken

Please set your "time" submodule to the "ghc" branch. It should always represent a stable release. -- Ashley On Wed, 2017-02-22 at 14:13 +, Phyx wrote: > The package has been fixed already but the submodule hasn't been > updated. For a quick fix just cd into libraries/time and checkout >

RE: Windows build broken

. If someone felt able to step up to doing it, it'd be great. Simon | -Original Message- | From: Kosyrev Serge [mailto:skosy...@ptsecurity.com] | Sent: 22 February 2017 14:18 | To: Simon Peyton Jones <simo...@microsoft.com> | Subject: Re: Windows build broken | | Simon, | | It pa

RE: Windows build broken

Tonight is fine – thank you! From: Phyx [mailto:loneti...@gmail.com] Sent: 22 February 2017 14:47 To: Simon Peyton Jones <simo...@microsoft.com> Cc: ghc-devs@haskell.org Subject: Re: Windows build broken Head of ghc is broken not head of time. Ghc is currently set to 6e202ed while

Re: Windows build broken

; > > > Simon > > > > *From:* Phyx [mailto:loneti...@gmail.com] > *Sent:* 22 February 2017 14:14 > *To:* Simon Peyton Jones <simo...@microsoft.com>; ghc-devs@haskell.org > *Cc:* Ashley Yakeley <ash...@semantic.org> > *Subject:* Re: Windows build broken

RE: Windows build broken

;; ghc-devs@haskell.org Cc: Ashley Yakeley <ash...@semantic.org> Subject: Re: Windows build broken The package has been fixed already but the submodule hasn't been updated. For a quick fix just cd into libraries/time and checkout master. I was hesitant to push the new submodule since we had

Re: Windows build broken

The package has been fixed already but the submodule hasn't been updated. For a quick fix just cd into libraries/time and checkout master. I was hesitant to push the new submodule since we hadn't branched yet for 8.2 On Wed, 22 Feb 2017, 14:09 Simon Peyton Jones via ghc-devs, <

Windows build broken

Please please please could some one fix this? On windows. It's frustrating being unable to build. Please please Simon libraries\time\lib\Data\Time\Clock\Internal\SystemTime.hs:57:5: error: Not in scope: data constructorFILETIME Perhaps you meantWin32.FILETIME(imported from

Re: Windows build broken -- again

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

Re: Windows build broken -- again

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:

Windows build broken -- again

Sigh. The Simon PJ Windows Buildbot reports "inplace/bin/ghc-stage1.exe" -optc-fno-stack-protector -optc-Wall -optc-Werror -optc-Wall -optc-Wextra -optc-Wstrict-prototypes -optc-Wmissing-prototypes -optc-Wmissing-declarations -optc-Winline -optc-Waggregate-return -optc-Wpointer-arith

RE: Aarrgh! Windows build broken again

Thanks for such a prompt reply -- I'll try that. Simon | -Original Message- | From: Matthew Pickering [mailto:matthewtpicker...@gmail.com] | Sent: 23 October 2016 00:13 | To: Simon Peyton Jones <simo...@microsoft.com> | Cc: ghc-devs@haskell.org | Subject: Re: Aarrgh! Windows

Re: Aarrgh! Windows build broken again

Erik has a patch which fixes this. I will merge it now. Matt On Sun, Oct 23, 2016 at 12:11 AM, Simon Peyton Jones via ghc-devs wrote: > On Windows with HEAD I get > > C:/code/HEAD/inplace/mingw/bin/ld.exe: cannot find -lnuma > > Sigh. This didn’t happen a day or two ago

Aarrgh! Windows build broken again

On Windows with HEAD I get C:/code/HEAD/inplace/mingw/bin/ld.exe: cannot find -lnuma Sigh. This didn't happen a day or two ago Simon ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Help! Windows build broken in teestsuite

Aargh! The Windows build is broken again. This time it’s the testsuite. It seems to be trying to run the test in a temp directory, and failing to find the directory. Thomie, could this be something to do with your work on the testsuite? Please fix! Or tell me what to revert.It leaves me

RE: Windows build broken

Thanks for a prompt fix! From: Tamar Christina [mailto:loneti...@gmail.com] Sent: 04 March 2015 00:47 To: Austin Seipp; Simon Peyton Jones Cc: ghc-devs@haskell.org Subject: Re: Windows build broken Hi Simon, Austin https://phabricator.haskell.org/D698 should fix the build. validate runs

Re: Windows build broken

This must be fallout from the VEH handler change I pushed earlier - 5200bdeb26c5ec98739b14b10fc8907296bceeb9. I'll try to fix/revert shortly. On Tue, Mar 3, 2015 at 4:30 PM, Simon Peyton Jones simo...@microsoft.com wrote: AAARGH! Windows build is broken again. Please can someone fix? In

Windows build broken

AAARGH! Windows build is broken again. Please can someone fix? In file included from rts\RtsMain.c:12:0: rts\PosixSource.h:31:0: error: __USE_MINGW_ANSI_STDIO redefined c:\code\head\inplace\mingw\bin\../lib/gcc/mingw32/4.5.2/../../../../include/_mingw.h:280:0: note: this is the location

Re: Windows build broken

Hi, Yes, sorry about that, I’m trying to reproduce it locally but no luck so far.. (waiting for a clean checkout to finish now) But the fix is probably to swap the definition of Excn.h and PosixSource.h in RtsMain.c or moving Excn.h to the bottom of the include list. Something in Excn.h

Windows build broken again: urgent

Alas. Alack. The Windows build is broken again. This time it's pretty fundamental: the stage2 compiler seg-faults every time it invokes the linker: *On GHCi startup *On every Template Haskell splice I don't know when this started, but I did a successful build at 23.10 on 24

RE: Windows build broken again: urgent

] | 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

Re: Windows build broken again: urgent

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

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. * Revert the commit. * Push the patch to master and notify the author. This style of early rollback will become more important as we grow

RE: Windows build broken again: urgent

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

Re: Windows build broken again: urgent

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

Re: Windows build broken in Linker.c

https://phabricator.haskell.org/D400 On Mon, Oct 27, 2014 at 1:34 PM, Gintautas Miliauskas gintau...@miliauskas.lt wrote: FYI, after the fix ghc builds again on Windows 32-bit, but validate.sh fails: rts\Linker.c: In function 'allocateImageAndTrampolines': rts\Linker.c:3657:31:

Re: Windows build broken in Linker.c

Sorry about this; merged - 208a0c207c1001da0fe63e9640e2a7e0e11c4aff (I actually only built the RTS to fix that build failure... I didn't ./validate with -Wall enabled. I'm to blame here!) On Wed, Oct 29, 2014 at 5:36 PM, Gintautas Miliauskas gintau...@miliauskas.lt wrote:

Re: Windows build broken in Linker.c

FYI, after the fix ghc builds again on Windows 32-bit, but validate.sh fails: rts\Linker.c: In function 'allocateImageAndTrampolines': rts\Linker.c:3657:31: error: unused parameter 'member_name' [-Werror=unused-parameter] pathchar* arch_name, char* member_name,

Re: Windows build broken in Linker.c

This is still not fixed, right? I've been working on the mingw gcc upgrade and testing on 32 bit, and this failure got me running in circles until I discovered that baseline was broken too... On Fri, Oct 17, 2014 at 2:00 AM, Simon Marlow marlo...@gmail.com wrote: I was working on a fix

Re: Windows build broken in Linker.c

I sent a patch to Austin to validate+commit earlier this week. On 24/10/2014 15:08, Gintautas Miliauskas wrote: This is still not fixed, right? I've been working on the mingw gcc upgrade and testing on 32 bit, and this failure got me running in circles until I discovered that baseline was

Re: Windows build broken in Linker.c

Gah, this slipped my mind. On it. On Fri, Oct 24, 2014 at 10:33 AM, Simon Marlow marlo...@gmail.com wrote: I sent a patch to Austin to validate+commit earlier this week. On 24/10/2014 15:08, Gintautas Miliauskas wrote: This is still not fixed, right? I've been working on the mingw gcc

Windows build broken in Linker.c

Simon Aargh! I think the Windows build is broken again. I think this is your commit 5300099ed Admittedly this is on a branch I'm working on, but it's up to date with HEAD. And I have no touched Linker.c! Any ideas? Simon rts\Linker.c: In function 'allocateImageAndTrampolines':

Re: Windows build broken in Linker.c

I see what's going on and am fixing it... The code broke 32-bit due to #ifdefery, but I think it can be removed, perhaps (which would be preferable). On Thu, Oct 16, 2014 at 3:43 PM, Simon Peyton Jones simo...@microsoft.com wrote: Simon Aargh! I think the Windows build is broken again. I

Re: Windows build broken in Linker.c

I was working on a fix yesterday but ran out of time. Frankly this code is a nightmare, every time I touch it it breaks on some platform - this time I validated on 64 bit Windows but not 32. Aargh indeed. On 16 Oct 2014 14:32, Austin Seipp aus...@well-typed.com mailto:aus...@well-typed.com

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

RE: Windows build broken (again)

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

Re: Windows build broken (again)

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),

Re: Windows build broken (again)

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

Windows build broken (again)

Sigh. The testsuite fails utterly on Windows, with thousands of identical errors = tc012(normal) 3039 of 4088 [1, 2677, 88] cd .\typecheck\should_compile 'C:/code/HEAD/inplace/bin/ghc-stage2.exe' -fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts

Re: Windows build broken (again)

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

Re: Windows build broken (again)

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

Windows build broken -- again!

Aaargh! My windows build is, once again, broken. The error is below. Could whoever broke it please fix it? Something to do with blocking_queue_hd perhaps? Please. Thanks Simon rts\win32\AsyncIO.c: In function 'awaitRequests': rts\win32\AsyncIO.c:289:23: error: 'blocking_queue_hd'

Re: Windows build broken -- again!

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

Windows build broken

Can someone fix this? This is breakage on Windows. It was fine yesterday. Simon cc1.exe: warnings being treated as errors rts\Linker.c: In function 'loadArchive': rts\Linker.c:2631:17: error: passing argument 1 of 'strlen' from incompatible pointer type

Re: Windows build broken

Looks like 5d7f59018703b94ebfe96cbef5574ec396a1c051 is the culprit. Simon M, perhaps you can look at this? I'm tied up in the 7.8 branch at the moment, but I can revert it temporarily at least (I imagine the fix is easy enough - if you can't get to it soon, I'll revert and fix it when I get a

Re: Windows build broken

Sorry, probably my fault. I've attached a patch that should fix it, which should get you going while I validate. Cheers, Simon On 04/04/2014 16:14, Simon Peyton Jones wrote: Can someone fix this? This is breakage on Windows. It was fine yesterday. Simon cc1.exe: warnings being treated as