Re: [ANNOUNCE] 7.10.3 release candidate 2 - problems compiling source on Mac OS with clang

George Colpitts writes: > As I mentioned above from brew: > > $ brew upgrade openssl > brew upgrade openssl > Error: openssl 1.0.2d_1 already installed > I see. Does the file in question exist? What does find /usr/local -iname asn1.h say? Cheers, - Ben

Re: [ANNOUNCE] 7.10.3 release candidate 2 - problems compiling source on Mac OS with clang

find /usr/local -iname asn1.h /usr/local/Cellar/nettle/2.7.1/include/nettle/asn1.h /usr/local/Cellar/openssl/1.0.1j/include/openssl/asn1.h /usr/local/Cellar/openssl/1.0.1j_1/include/openssl/asn1.h /usr/local/Cellar/openssl/1.0.1l/include/openssl/asn1.h

Re: [ANNOUNCE] 7.10.3 release candidate 2 - problems compiling source on Mac OS with clang

As I mentioned above from brew: $ brew upgrade openssl brew upgrade openssl Error: openssl 1.0.2d_1 already installed Thanks On Mon, Nov 16, 2015 at 6:00 AM, Ben Gamari wrote: > George Colpitts writes: > > > I did get compiling from source

Re: Implementation idea for unboxed polymorphic types

> But I don't see why you'd need quoting at constructor calls. Couldn't you > just have a type class like `PointFamily`? This is exactly right, my memory has failed me. My initial implementation didn't use the type family trick, I had further attempts that use type families but honestly I don't

Further custom type error questions

While preparing some additional documentation for Iavor's custom type errors work (which has been merged; thanks Iavor!) I noticed that Dominique Devriese has raised some additional questions on the proposal [1]. In particular, Dominique suggests that perhaps TypeError should simply be of kind

process librarry

Michael My Windows build (sh validate in a clean tree) is still falling over as follows, on Windows. Would it be possible to fix the process library to stop this happening? Thanks Simon libraries\process\System\Process\Internals.hs:106:16: warning: Defined but not used: data constructor

Re: Further custom type error questions

Hello, I imagine people wanting to do things as in the example below. If we were to use only `TypeError` constraints, then we'd have to mostly use the class system to do type-level evaluation. It doesn't seem obvious how to do that with just `TypeError` of kind constraint, unless all evaluation

Re: process librarry

Can you try updating the submodule to the latest master and see if that fixes it for you? On Tue, Nov 17, 2015, 1:25 AM Simon Peyton Jones wrote: > Michael > > My Windows build (sh validate in a clean tree) is still falling over as > follows, on Windows. Would it be

Re: [ANNOUNCE] 7.10.3 release candidate 2 - problems compiling source on Mac OS with clang

My understanding is that they now use libre ssl. So definitely not OpenSSL. If you want open ssl instead you need to install it via brew or the like On Monday, November 16, 2015, George Colpitts wrote: > Sorry, it seems that this is a known problem with Mac OS 10.11.

Re: [ANNOUNCE] 7.10.3 release candidate 2 - problems compiling source on Mac OS with clang

Apple has started to move away from OpenSSL for quite a while. This post summarises it quite nicely http://rentzsch.tumblr.com/post/33696323211/wherein-i-write-apples-technote-about-openssl-on In recent times, you could add as a reason for avoiding OpenSSL its shaky security track record.

Re: [ANNOUNCE] 7.10.3 release candidate 2 - problems compiling source on Mac OS with clang

George Colpitts writes: > I did get compiling from source to work on the Mac. Unfortunately I'm not > sure what the problem was. > > I now see a new problem, not sure if it is a ghc problem or a library > problem: > > cabal install HsOpenSSL > ... > Building