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: Compiling on OpenBSD-current

https://phabricator.haskell.org/D2673 is responsible. It adds CONF_LD_LINKER_OPTS_STAGE0 to $1_$2_$3_ALL_LD_OPTS, which is documented as "Options for passing to plain ld", which is okay. But just below that the same variable $1_$2_$3_ALL_LD_OPTS is added (with -optl prefixes attached) to

Re: Compiling on OpenBSD-current

Reid Barton writes: > https://phabricator.haskell.org/D2673 is responsible. It adds > CONF_LD_LINKER_OPTS_STAGE0 to $1_$2_$3_ALL_LD_OPTS, which is > documented as "Options for passing to plain ld", which is okay. But > just below that the same variable $1_$2_$3_ALL_LD_OPTS is

testsuite broken

Yikes. I can’t run the testsuite on Linux (debian ? I think…). See below. I installed python3 by saying apt-get install python3 And indeed python3 --version Python 3.2.3 This is bad. Can anyone help? Simon PYTHON="python3" "python3" ../../driver/runtests.py -e

Re: testsuite broken

Simon Peyton Jones via ghc-devs writes: > Yikes. I can’t run the testsuite on Linux (debian ? I think…). See below. > I installed python3 by saying > apt-get install python3 > And indeed > > python3 --version > > Python 3.2.3 For the record I've opened #12909

RE: testsuite broken

Ben is on it too: #12909 From: Phyx [mailto:loneti...@gmail.com] Sent: 01 December 2016 15:49 To: Simon Peyton Jones ; ghc-devs@haskell.org Subject: Re: testsuite broken Bah, String handling in python is a complete mess. In any case, we dropped support for 2 so we can

How to inline early in a GHC plugin?

I'm implementing a GHC plugin that installs a `BuiltInRule` that does the work, and I'd like to learn how to inline more flexibly. Given an identifier `v`, I'm using `maybeUnfoldingTemplate (realIdUnfolding v)` to get a `Maybe CoreExpr`. Sometimes this recipe yields `Nothing` until a later

Re: [GHC] #11744: Latest Xcode update violates POSIX compliance of `nm -P`

I can confirm that what Ben says is true for me using XCode 8.1 On Thu, Dec 1, 2016 at 6:21 PM GHC wrote: > #11744: Latest Xcode update violates POSIX compliance of `nm -P` > -+-- > Reporter: hvr

Re: Compiling on OpenBSD-current

I've been hit by this during 8.0.2 rc1 binary preparation so if nobody else nor you find a time to fix that sooner I'll hopefully find some time during this weekend to have a look into it. I'm pretty sure this is fairly recent breakage on OpenBSD... Cheers, Karel On 12/ 1/16 12:21 PM, Adam

Compiling on OpenBSD-current

Hi When Compiling on OpenBSD-Current I get the follow error, what do i need to do to fix this? Cheers Adam ===--- building phase 0 gmake --no-print-directory -f ghc.mk phase=0 phase_0_builds gmake[1]: Nothing to be done for 'phase_0_builds'. ===--- building phase 1 gmake --no-print-directory -f