Re: More windows

ur is new. > > > > Simon > > > > *From:* Phyx [mailto:loneti...@gmail.com] > *Sent:* 04 October 2017 14:17 > *To:* Simon Peyton Jones <simo...@microsoft.com>; ghc-devs@haskell.org > *Subject:* Re: More windows > > > > This looks like a file lock is

Re: More windows

This looks like a file lock issue. Just to double check, but do you have the build folder excluded from the antivirus scanner? On Wed, Oct 4, 2017, 13:57 Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote: > Now in my Windows build, staring with “sh validate –fast –no-clean” I get > >

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

Re: Feedback request regarding HSOC project (bringing sanity to the GHC performance test-suite)

ince the current implementation doesn't allow for the data to live together in the same repo. > > Hopefully this answers some questions; I'll make sure this sort of > information is available somewhere so that later users can find these > answers again. Thanks for your though

Re: Feedback request regarding HSOC project (bringing sanity to the GHC performance test-suite)

Hi Jared, First off, thanks for all the hard work on this. I checked out your branch and made a run, I noticed at the end it had Framework failures: . ./perf/compiler/all.T [] (unexpected indent (, line 298)) so I assume none of the perf tests were run? Though I do see a .git/refs/notes/perf,

Re: dll-split

That's certainly a possibility, though note that this is only an issue for compiling stage2, not end user programs. Since it's only for compiling ghc we don't have to include it in the bindist so license would be less of an issue I think. I'll modify the scripts to pull it automatically when I

Re: [ANNOUNCE] GHC 8.2.1 release candidate 1

Hi Ben, The windows build is unusable. The settings file has $TopDir expanded and hard-coded to the build path on drydock. Tamar On Mon, 10 Apr 2017, 08:14 Boespflug, Mathieu, wrote: > Hi Ben, > > this is great news! I'm particularly keen on learning more about two > points you

Re: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10 15019+)

, 09:18 Simon Peyton Jones via ghc-devs, < ghc-devs@haskell.org> wrote: > Yikes that sounds bad! > > > > I just wanted to raise awareness and offer myself to do guided grunt work > (if there is any) to push out a hotfix/inplace patch release for GHC 8.0.2. > > > >

Re: FW: GHC on Windows 10 15019+

On Fri, 10 Mar 2017, 13:15 Simon Peyton Jones via ghc-devs, < ghc-devs@haskell.org> wrote: > Phyx and friends: does this ring a bell? Do we have a ticket? > > -Original Message- > From: Glasgow-haskell-users [mailto: > glasgow-haskell-users-boun...@haskell.org] On

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, wrote: > Simon Peyton Jones via ghc-devs writes: > > > My windows build is more broken than usual. I can't even build

Re: Windows build failing in a new way

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, <loneti...@gmail.com> wrote: > That said, running the build on HEAD it seems that the

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 and

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: MSYS2 update (those who build on Windows please read)

Hi all, MSYS2 maintainers have agreed that the change by Cygwin constitudes a regression for the MSYS2 project and patched out the changes. It's now safe to upgrade MSYS2 again. Tamar On Mon, Feb 20, 2017 at 3:58 PM, Phyx <loneti...@gmail.com> wrote: > Hi Windows devs, > >

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

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

MSYS2 update (those who build on Windows please read)

Hi Windows devs, February comes with a major change in behavior for MSYS2/Cygwin. Tools such as awk/sed etc now use binary mode unless on a text mount: https://cygwin.com/ml/cygwin-announce/2017-02/msg00036.html This is problematic because GHC etc only use the underlying OS to determine how to

Re: Cannot build GHC using the Newcomers guide

course, this only works if you are using nix! > > Matt > > On Thu, Jan 26, 2017 at 5:18 PM, Phyx <loneti...@gmail.com> wrote: > > Can I ask a silly question. I can't seem to find where stack is > recommended > > for ghc development on the newcomers page, but why is it

Re: Cannot build GHC using the Newcomers guide

Can I ask a silly question. I can't seem to find where stack is recommended for ghc development on the newcomers page, but why is it? I don't want to start another flame war but I can't imagine any scenario where this is useful. As far as I understand the whole benefit of stack is the curated

Re: [GHC] #13035: GHC enters a loop when partial type signatures and advanced type level code mix

Ah, great thanks! On Fri, 6 Jan 2017, 20:32 GHC, wrote: > #13035: GHC enters a loop when partial type signatures and advanced type > level code > mix > -+- > Reporter: xcmw |

Re: Trac to Phabricator (Maniphest) migration prototype

In response to no# 2, I was looking at this my self since I think separate fields would definitely be useful. It seems you can customize the form design on phabricrator. I think it would definitely be worth it to make a new form layout resembling the layout of track. I don't know how it stores it

Re: Trac to Phabricator (Maniphest) migration prototype

Hi Matthew, Great work! I must admit I'm one of the few that generally likes Trac but I'm liking this quite a lot. Just two questions, Is it possible for those like me who have a different username on trac and phabricator to get mapped correctly? And how does the ticket creation process look?

Re: Telemetry (WAS: Attempt at a real world benchmark)

On Fri, Dec 9, 2016 at 3:53 PM, Ben Gamari wrote: > Simon Peyton Jones via ghc-devs writes: > > > Just to say: > > > > > > · Telemetry is a good topic > > > > · It is clearly a delicate one as we’ve already seen from two widely > > differing

Re: testsuite broken

Bah, String handling in python is a complete mess. In any case, we dropped support for 2 so we can remove the u prefixes. It seems that the Unicode syntax in python 3 was dropped in python 3.0 and reintroduced on 3.3. We were all using 3.5 to test. To get you going again quickly, You can

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

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

Re: Default options for -threaded

Oh, this is surprising, I must admit I haven't tried forkIO, but with forkOS is doesn't move the threads across capabilities. Do you know if this is by design or a bug? On Sat, Oct 8, 2016 at 6:13 PM, Eric Seidel wrote: > I would prefer keeping -N1 as a default, especially now

Re: Default options for -threaded

Oops, sorry, only just now seen this. It seems my overly aggressive filters couldn't decide where to put the email :) I do agree to some extend with this. I'd prefer if I made a mistake for my system not to hang. The one downside to this default though is that you can't just hand a program over

Re: Create a ghc-simple-patch-propose list? Re: Notes from Ben's "contribute to ghc" discussion

I dislike this approach, having to already deal with a project that does patches via mailing lists it is very hard to follow conversations. As soon as multiple people get involved things fall apart. I have multiple mailing rules and other things just so I can keep track of comments. And then

Re: Notes from Ben's "contribute to ghc" discussion

>> >> ·Auto-push: Ability to push to Phab and have it committed >> automatically if it validates. > > \o/ How would this work? Could there be a cooldown period? e.g. commits sit a day before being auto-committed? Validate really only validates Linux x86_64. The situation is already quite

Re: Test T12504 on Windows

The new output is correct. hsc2hs was patched to fix the error messages it gives. We missed a test it seems. I'll update the test output when I get home. Thanks Simon, Tamar On Tue, Sep 20, 2016, 23:06 Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote: > Test hsc2hs/T12504 is

Re: building ghc-8.0 branch on Win10

Hi Josh, Yes you are hitting a bug in configure that was exposed due to changes in msys. Cherry-pick this commit to your branch https://ghc.haskell.org/trac/ghc/ticket/12487 Tamar On Mon, Sep 19, 2016, 12:24 Josh Berman wrote: > Hi, > > I was able to build the "master"

Re: Action Required: Status of Harbormaster for Differentials

Hi Ben, Out of curiosity which platforms will be getting harbormaster support? Is this only Linux x86_64? Any plans to expand this in the future to all Tier 1 platforms? Cheers, Tamar On Fri, Aug 26, 2016, 22:39 Ben Gamari wrote: > Joachim Breitner

RE: Windows build

Hi Simon, Thomie changed it so the in place gcc can be called from the testsuite. The tests should pass now. Kind regards, Tamar Sent from my Mobile On Jul 8, 2016 23:02, wrote: > Hi Simon, > > > > For these tests it shouldn’t matter much so I guess I can change them. > >

Re: Cross-compiling Template Haskell via -fexternal-interpreter and IPC

> However, compiling TH by using wine and ghc-iserver.exe fails because the file descriptor ids that GHC passes as arguments to "wine ghc-iserv.exe" don't make sense in the emulated windows world. Just as a note, On Windows we don't pass FDs (As in the posix file descriptor) to the child process.

Re: Linker.c broken

Let’s re-enable it. Or: how can I selectively re-enable it for in my > validate.mk? > > > > *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of *Phyx > *Sent:* 04 July 2016 13:05 > *To:* Erik de Castro Lopo <mle...@mega-nerd.com>; ghc-devs < > ghc-d

Re: Linker.c broken

a ticket with more information on it and what I found back then, but haven't been able to progress. It might be that they've just fixed it in the mean time. On Mon, Jul 4, 2016, 12:58 Erik de Castro Lopo <mle...@mega-nerd.com> wrote: > Phyx wrote: > > > I can build and validat

Re: Linker.c broken

I can build and validate in about an hour myself using 9 jobs on a core i7. If I revert the change in the testsuite preventing parallel runs for Windows. Tamar On Mon, Jul 4, 2016, 12:26 Ben Gamari wrote: > "Boespflug, Mathieu" writes: > > > On 4 July 2016

Re: msys2 64 bit: help help!

Hi Simon, Andrey > > 3. After this step, starting a shell failed altogether with > "c:/msys64/mingw64_shell.bat is > > not recognised as an internal or external command". And sure enough, > there is no such file. > > Presumably it existed in step 1. So perhaps step 2 deleted it? > > [...] > >

CoreToStg Asserts

Hi *, I'm hoping someone could help me understand what the asserts in CoreToStg on line 240 and 216 are trying to tell me. I hit both of them while trying to compile libraries as dyn. WARNING: file compiler\stgSyn\CoreToStg.hs, line 250 $trModule2 False True ghc-stage1.exe: panic! (the

Re: Build failing

Hi Simon, I have made a diff to fix it but it hasn't been reviewed yet https://phabricator.haskell.org/D1878 Regards, Tamar Sent from my Mobile On Feb 2, 2016 12:07 PM, "Simon Peyton Jones" wrote: > A clean Windows build fails. See below. help! > > Simon > > > >

Re: Linker questions

Hi Edward, Thanks for the information, it really helped make it more clear to me what's going on. I would ideally like to get these validate errors on Windows down to 0 (without marking them as expected fail). So I will probably make a ticket for this. Cheers, Tamar On Thu, Aug 20, 2015 at

Re: GHC on Windows (extended/broad discussion)

Hi All, Sorry for the late reply, I need to adjust my mail filtering rules to let these mails go to my inbox as well. I have also taken a few passes through the windows trac and there are a lot of issues with someone assigned to them but with no activity so a while on them. I was also wondering

<    1   2