I put some notes on trac. I’ll see about updating build notes later.
I did find some stuff in the Mach linker that needs to be handled
differently on gcc vs clang on Mac. And likely needs a patch so it also
builds clean with gcc
On Thu, Dec 28, 2017 at 10:26 AM Ben Gamari wrote:
> Carter Scho
Carter Schonwald writes:
> digging around in configure.ac it looks like i need to set CC_STAGE0 env
> variable to my desired CC :)
>
> hope this helps other folks... but it definiely seems like the current
> logic for CC_STAGE0 is more brittle than for CC
>
Indeed, I've realized over the last few
digging around in configure.ac it looks like i need to set CC_STAGE0 env
variable to my desired CC :)
hope this helps other folks... but it definiely seems like the current
logic for CC_STAGE0 is more brittle than for CC
On Sun, Dec 24, 2017 at 5:02 PM, Carter Schonwald <
carter.schonw...@gmail.c
hey All, the current settings for warnings etc for ghc validate do not work
on mac,
this is because some gcc flag isn't in clang, or vice versa, or some
version of gcc related matter
the relevant error is:
error: unknown warning option '-Werror=unused-but-set-variable'; did you
mean '-Werror=unu
Sorry if this has been addressed recently, but I can't validate right now, due
to a build failure from -Werror in C code in primitive:
> "inplace/bin/ghc-stage2" -optc-Werror -optc-Wall
> -optc-Ilibraries/primitive/cbits -optc-O3 -optc-ftree-vectorize
> -optc-fomit-frame-pointer -optc-msse2
>
