Re: GHC HEAD now needs extra tools to build libffi?

Thomas Jakway writes: > Anyone else getting linker errors? > > > This is after running > > make clean && make distclean && find . -name "*.o" -type f -delete && > find . -name "*.hi" -type f -delete > > then > > ./boot && ./configure && make -j5 > > (ghc-new is not a new

Re: GHC HEAD now needs extra tools to build libffi?

Thomas Jakway writes: > Hm, so it's definitely not anything I changed. I just cloned and built > it and got the same problem (7109fa8157f3258912c947f28dab7617b5e5d281). > Alright, I'm trying to replicate. Cheers, - Ben signature.asc Description: PGP signature

Re: GHC HEAD now needs extra tools to build libffi?

Build flavor is devel2, of course. On 10/03/2017 04:42 PM, Ben Gamari wrote: Can you confirm which commit you are on? On October 3, 2017 4:36:48 PM EDT, Thomas Jakway wrote: Not sure. I ran `git submodule update --init --recursive` and git status says everything's

Re: GHC HEAD now needs extra tools to build libffi?

Hm, so it's definitely not anything I changed. I just cloned and built it and got the same problem (7109fa8157f3258912c947f28dab7617b5e5d281). On 10/03/2017 04:42 PM, Ben Gamari wrote: Can you confirm which commit you are on? On October 3, 2017 4:36:48 PM EDT, Thomas Jakway

Re: More windows

Oh sorry, I missed the ls line, I'll try building master. On Wed, Oct 4, 2017 at 5:24 PM, Simon Peyton Jones wrote: > As you’ll see the directory is empty when the crash happens. And yes the > folder is excluded. > > > > Also this behaviour is new. > > > > Simon > > > >

RE: More windows

As you’ll see the directory is empty when the crash happens. And yes the folder is excluded. Also this behaviour is new. Simon From: Phyx [mailto:loneti...@gmail.com] Sent: 04 October 2017 14:17 To: Simon Peyton Jones ; ghc-devs@haskell.org Subject: Re: More windows

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

More windows

Now in my Windows build, staring with "sh validate -fast -no-clean" I get [230 of 232] Compiling Distribution.PackageDescription.Parsec ( libraries\Cabal\Cabal\Distribution\PackageDescription\Parsec.hs, bootstrapping\Distribution\PackageDescription\Parsec.o ) [231 of 232] Compiling

RE: Windows build broken

I’m in a shell inside emacs. My $SHELL variable (which emacs uses to invoke it) is c:/msys64/usr/bin/bash.exe Should it be something else? run 'export MSYSTEM=MINGW64' to change subsystem. That worked. Should I add it to my .bashrc, or are you going to do something else? Thanks

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: GHC rewrite rule type-checking failure

The new bit here is that `$dC'` is not found via matching in the LHS, but rather by instance resolution from `k`, which does appear explicitly in the LHS Well this would be something qualitatively new. We don’t that ability in rules; and it’s far from clear to me what it would mean anyway. I