GHC 8.0.1-rc4 source tarball availability

[Carter Schonwald]

(NB: i would like any folks who don't have a gcc6 dylib as i mention above
to please stress test it out :) ), though it didn't seem to interfere with
builds  when i deleted gcc6 and had it go through its paces

On Sat, Apr 23, 2016 at 8:05 PM, Carter Schonwald <
carter.schonwald at gmail.com> wrote:

> I'll try to collect my thoughts and tease out what did/didn't work
> tomorrow,
> in the mean time, here's a build I believe should work for everyone on mac
> and should have full docs,
>
> http://wellposed-carter-files.s3.amazonaws.com/opensource/ghc/releasebuild-unofficial/ghc-8.0.0.20160421-x86_64-apple-darwin.tar.xz
>
> shasum -a512 ghc-8.0.0.20160421-x86_64-apple-darwin.tar.xz
> 969eb2914b9c7c31bcdfb814aac34f0dcd9d6c8d7b9e7affe1605985e9de543d911dc6dae0fa05a32da12150d56488e56ad6fbf4d1f818ec84f7a4759d876c95
>  ghc-8.0.0.20160421-x86_64-apple-darwin.tar.xz
>
> one niggling issue is that, at least based upon the output of otool -L,
> the builds point to  /usr/local/lib/gcc/6/libgcc_s.1.dylib
> (my userland GCC leaking through)
> and I *believe* but could be wrong that its better to have it point
> to /usr/lib/libgcc_s.1.dylib or something?
> otoh, the otool -L output of those respective things are VERY different
>
> I will investigate that further, though its orthogonal to my doc building
> confusion that I still need to work out what happened with
>
>
> On Sat, Apr 23, 2016 at 6:57 PM, Ben Gamari <ben at well-typed.com> wrote:
>
>> Carter Schonwald <carter.schonwald at gmail.com> writes:
>>
>> > Thomie (Thomas M?) pointed out that there may have been a
>> "are-validating"
>> > make file in my /mk/ dir that could have been messing with things.
>> >
>> > i've gotten a build i'm happy with, i'm now seeing if i can tweak it to
>> > have the otool -L output favor stuff in /usr/lib (ie mac standard
>> stuff) vs
>> > userland overlays for some basic linker stuff
>> >
>> Could you elaborate a bit here?
>>
>> If there are manual tweaks applied to the build then we need to make
>> sure they are documented (or ideally scripted, with the script in a
>> publicly accessible, version controlled location), especially if we
>> want to offer your build in some "official" capacity.
>>
>> Cheers,
>>
>> - Ben
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20160423/f8ca8bc6/attachment-0001.html>