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 mentionin

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

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

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

. Or run 'export MSYSTEM=MINGW64' to change subsystem. The recent llvm changes now force the host validation on all targets, I'll add msys when I get home. Kind regards, Tamar On Wed, Oct 4, 2017, 11:19 Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote: > My Wind

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/',

Windows build

Dear Windows folk, Here's my testsuite output for a clean build on Windows last night. Rather a lot of failures - can we reduce them? Simon SUMMARY for test run started at Wed Apr 5 01:37:30 2017 GMTST 0:50:08 spent to go through 5822 total tests, which gave rise to 16777 test cases,

RE: Windows build failing in a new way

… .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

RE: Windows build failing in a new way

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.

RE: Windows build failing in a new way

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

RE: Windows build failing in a new way

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

Re: Windows build failing in a new way

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

Re: Windows build failing in a new way

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, <b...@smart-cactus.org> wrote: > Simon Peyton Jones via ghc-devs <ghc-devs@haskell.org> writes: > > > My windows build is more broken than us

Re: Windows build failing in a new way

Simon Peyton Jones via ghc-devs <ghc-devs@haskell.org> 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 local

Re: Windows build failing in a new way

il.com> wrote: > > 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 f

Re: Windows build failing in a new way

2017, 16:38 Phyx, <loneti...@gmail.com> wrote: > 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

Re: Windows build failing in a new way

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

Windows build failing in a new way

My windows build is more broken than usual. I can't even build a GHC. Please, could someone fix this? I'm getting desperate. Simon libtool: compile: C:/code/HEAD/inplace/mingw/bin/gcc.exe -DHAVE_CONFIG_H -I. -I.. -I. -I../include -Iinclude -I../src -Wall -Werror -fno-stack-protector -w

Re: Windows build broken again

Simon Peyton Jones via ghc-devs <ghc-devs@haskell.org> 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

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 <ghc-devs@haskell.org> 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

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: C:\code\HEAD\inplace\lib\package.conf.d

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

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

by doing enough I/O. Thanks, Tamar From: Simon Peyton Jones Sent: Tuesday, January 17, 2017 08:13 To: Phyx Cc: ghc-devs Subject: Windows build Hi Tamar The current state of a clean Windows build has improved – but still has multiple failures.  See below Thanks for your work on this. I can send

Windows build

Hi Tamar The current state of a clean Windows build has improved - but still has multiple failures. See below Thanks for your work on this. I can send more details if that'd be helpful Simon Unexpected failures: plugins/plugins07.run plugins07 [bad exit code] (normal) plugins/T10420

Re: Windows build again

Simon Peyton Jones via ghc-devs <ghc-devs@haskell.org> writes: > Windows build is broken in a new way. > When I run validate I end up with sh.exe processes that consume a full CPU > forever. See the process log below. > > Note that these are not GHC processes: the

RE: Windows build

n stderr? The errors are hard to reproduce on all machines so logs help a lot. Thanks, Tamar From: Simon Peyton Jones via ghc-devs Sent: Wednesday, November 30, 2016 22:50 To: ghc-devs@haskell.org Subject: Windows build Thanks for all the work you’ve been doing on the Windows build. As requested by

Windows build

Thanks for all the work you've been doing on the Windows build. As requested by Tamar I removed ghc-tarballs, and reconfigured. Then I built from scratch. I get the following testsuite failures Simon Unexpected failures: ghci/prog003/prog003.runprog003 [bad exit code] (ghci

RE: windows build

) | -Original Message- | From: Ben Gamari [mailto:b...@well-typed.com] | Sent: 17 November 2016 15:24 | To: Simon Peyton Jones <simo...@microsoft.com> | Subject: RE: windows build | | Simon Peyton Jones <simo...@microsoft.com> writes: | | > OK thank you. | > | > Meanwhil

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

RE: Windows build

;; ghc-devs@haskell.org Subject: Re: Windows build And uname -a? If you're on anything higher than 2.5.1 the runtime has a regression per Ben's email. If you're not. Try using python3 for testing. Make test PYTHON=/usr/bin/python3 On Tue, Oct 18, 2016, 11:30 Simon Peyton Jones <simo...@micr

Re: Windows build

ypecheck/should_fail$ python2 --version > > Python 2.7.11 > > .../typecheck/should_fail$ python3 --version > > Python 3.4.3 > > .../typecheck/should_fail$ > > > > *From:* Phyx [mailto:loneti...@gmail.com] > *Sent:* 18 October 2016 11:07 > *To:* Simon Peyton

RE: Windows build

.../typecheck/should_fail$ python3 --version Python 3.4.3 .../typecheck/should_fail$ From: Phyx [mailto:loneti...@gmail.com] Sent: 18 October 2016 11:07 To: Simon Peyton Jones <simo...@microsoft.com>; ghc-devs@haskell.org Subject: Re: Windows build Hi Simon, What does which python 2 and

Re: Windows build

Hi Simon, What does which python 2 and which python 3 return? Along with uname -a? Tamar On Tue, Oct 18, 2016, 10:58 Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote: > On Windows I now get a lot of framework failures, below. > > I have not tried them all, but some work fine when

Windows build

On Windows I now get a lot of framework failures, below. I have not tried them all, but some work fine when run individually; e.g. make TEST=AssocTyDef09 Simon Unexpected passes: rts/T7037.run T7037 [unexpected] (normal) Unexpected failures: ghci/prog003/prog003.run prog003 [bad

Re: Aargh! Windows build is broken AGAIN

gt; *To:* Simon Peyton Jones via ghc-devs <ghc-devs@haskell.org> > *Subject:* RE: Aargh! Windows build is broken AGAIN > > > > Hi Simon, > > > > Sorry for the broken build again. Since your last email I do run a nightly > build, but you were about

RE: Aargh! Windows build is broken AGAIN

ct: RE: Aargh! Windows build is broken AGAIN Hi Simon, Sorry for the broken build again. Since your last email I do run a nightly build, but you were about an hour and a half before today’s build! Anyway, I believe the offending commit is 8c6a3d68c0301bb985aa2a462936bbcf75

RE: Aargh! Windows build is broken AGAIN

Seems I forgot to do a reply all… From: loneti...@gmail.com Sent: Friday, October 14, 2016 23:23 To: Simon Peyton Jones via ghc-devs Subject: RE: Aargh! Windows build is broken AGAIN Hi Simon, Sorry for the broken build again. Since your last email I do run a nightly build, but you were about

Re: Aargh! Windows build is broken AGAIN

Simon Peyton Jones via ghc-devs wrote: > I really wish I did not have to be the Windows integration server. > Currently, from a clean build of HEAD, I'm getting > > libraries\base\GHC\Event\TimerManager.hs:62:3: error: > > error: #error not implemented for this operating system > > #

RE: Aargh! Windows build is broken AGAIN

that TimerManager which is defined for POSIX only. Reverting that should get you building again. Cheers, Tamar From: Simon Peyton Jones via ghc-devs Sent: Friday, October 14, 2016 22:38 To: ghc-devs@haskell.org Subject: Aargh! Windows build is broken AGAIN I really wish I did not have

Aargh! Windows build is broken AGAIN

I really wish I did not have to be the Windows integration server. Currently, from a clean build of HEAD, I'm getting libraries\base\GHC\Event\TimerManager.hs:62:3: error: error: #error not implemented for this operating system # error not implemented for this operating system

RE: Windows build

Indeed – it works great now. Thank you! I have a working Windows build on my Surface Book. Hooray. Many thanks to everyone who helped. Simon From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Phyx Sent: 09 July 2016 18:00 To: Simon Peyton Jones via ghc-devs <ghc-d

RE: Windows build

ess 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 them. While

RE: Windows build

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

Windows build

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)

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

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

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 file

Re: Windows build gotchas

On 1. 1. 2015 19:01, Martin Foster wrote: Hello all, I've been spending some of my winter break trying my hand at compiling GHC, with a mind to hopefully contributing down the line. I've got it working, but I ran into a few things along the way that I figure might be worth fixing and/or

Re: Windows build gotchas

On Thu, Jan 1, 2015 at 6:42 PM, Herbert Valerio Riedel hvrie...@gmail.com wrote: I noticed that the cabal output made reference to C:\Users\Martin\AppData\Roaming\cabal\, so tried moving that out of the way, but it only made the problem worse. I did figure it out eventually: in addition

Windows build gotchas

Hello all, I've been spending some of my winter break trying my hand at compiling GHC, with a mind to hopefully contributing down the line. I've got it working, but I ran into a few things along the way that I figure might be worth fixing and/or documenting. In the approximate order I

Re: Windows build gotchas

Hello Martin, Here's just some minor additional context information... On 2015-01-01 at 19:01:53 +0100, Martin Foster wrote: [...] - I note ./sync-all --help says, under Flags, that --windows also clones the ghc-tarballs repository (enabled by default on Windows), and I've

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

Yes, ideally this would have been caught by a Windows build bot. On Mon, Dec 1, 2014 at 4:34 PM, Simon Peyton Jones simo...@microsoft.com wrote: Indeed. But each bisect takes quite a while. So my attention switches and it takes a while to get back. I was hoping some machine might do

Re: Windows build broken in Linker.c

, Oct 16, 2014 at 3:43 PM, Simon Peyton Jones simo...@microsoft.com mailto:simo...@microsoft.com wrote: Simon Aargh! I think the Windows build is broken again. I think this is your commit 5300099ed Admittedly

Re: Windows build broken in Linker.c

PM, Simon Peyton Jones simo...@microsoft.com mailto:simo...@microsoft.com wrote: Simon Aargh! I think the Windows build is broken again. I think this is your commit 5300099ed Admittedly this is on a branch

  1   2   >