On Mon, 19 Jun 2017 13:31:33 + (UTC) Gianfranco Costamagna
wrote:
> Hello,
> >Now that we shipped strech, I really would like to see llvm 3.7 removed.
> >Can we go ahead now ?
>
>
> as said, with ghc 8.0.1 and 8.0.2 this seems a little impossible, but as
> Clint said on debian-haskell
>
>
Hello,
>Now that we shipped strech, I really would like to see llvm 3.7 removed.
>Can we go ahead now ?
as said, with ghc 8.0.1 and 8.0.2 this seems a little impossible, but as Clint
said on debian-haskell
>> last thing: should we switch llvm? wrt #850915
>I think the GHC 8.2 release candidates
Hello
Now that we shipped strech, I really would like to see llvm 3.7 removed.
Can we go ahead now ?
Thanks
S
___
Pkg-haskell-maintainers mailing list
Pkg-haskell-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/list
Hello
>Probably need to backport this upstream commit:
>
>https://git.haskell.org/ghc.git/commitdiff/672314cbeb8ac386a58f17dc4650dbdf4c55d8b5
probably not only that one, but at least 3 commits
Unfortunately when I expressed the idea (and the commits) over irc on
#debian-haskell or whatever
I
On Wed, 11 Jan 2017 09:21:54 +0100 Sylvestre Ledru wrote:
> Source: ghc
> Severity: important
>
> Hello,
>
> The armel build issue on 3.8 and 3.9 has been fixed thanks to a fix in
> libstdc++.
> ghc can now change llvm version.
>
> This is the last package using llvm 3.7, blocking its removal.
Source: ghc
Severity: important
Hello,
The armel build issue on 3.8 and 3.9 has been fixed thanks to a fix in
libstdc++.
ghc can now change llvm version.
This is the last package using llvm 3.7, blocking its removal.
(note that I stopped caring about 3.7 more than a year ago, it is far behing