Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

2017-06-18 Thread Sylvestre Ledru
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/listinfo/pkg-haskell-maintainers


Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

2017-06-19 Thread Gianfranco Costamagna
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 are targeting LLVM 4.0.


so for Buster we will probably ship 8.2 or something even newer.

But for now, I don't think such change is worth the effort, specially because 
it will probably introduce
bugs because this will be an untested configuration.
I really hope with 8.2 to make this one disappear :)
(I guess it will be released in some months)

G.

___
Pkg-haskell-maintainers mailing list
Pkg-haskell-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers


Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

2017-01-11 Thread Sylvestre Ledru
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 
3.8 or 3.9
in term of maintenance/support).

Sylvestre

___
Pkg-haskell-maintainers mailing list
Pkg-haskell-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers


Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

2017-01-11 Thread Emilio Pozuelo Monfort
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.
> (note that I stopped caring about 3.7 more than a year ago, it is far behing 
> 3.8 or 3.9
> in term of maintenance/support).

Probably need to backport this upstream commit:

https://git.haskell.org/ghc.git/commitdiff/672314cbeb8ac386a58f17dc4650dbdf4c55d8b5

Cheers,
Emilio

___
Pkg-haskell-maintainers mailing list
Pkg-haskell-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers


Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

2017-01-11 Thread Gianfranco Costamagna
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 got a nack, because diverging from upstream in the default toolchain version 
is a no-go,
and moreover it would require probably a lot of binNMUs in the arm* 
architectures for the whole
haskell stack.

Upstream can fix bugs when llvm 3.7 is used, now when we diverge in such 
important key packages.

(this is a sum of the discussion I recall right now, I can search irc logs if 
needed)

G.

___
Pkg-haskell-maintainers mailing list
Pkg-haskell-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers


Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

2018-04-09 Thread Gianfranco Costamagna
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
> 
> >> last thing: should we switch llvm? wrt #850915
> >I think the GHC 8.2 release candidates are targeting LLVM 4.0.
> 
> 
> so for Buster we will probably ship 8.2 or something even newer.
> 
> But for now, I don't think such change is worth the effort, specially because 
> it will probably introduce
> bugs because this will be an untested configuration.
> I really hope with 8.2 to make this one disappear :)
> (I guess it will be released in some months)
> 

3.7 can now be removed, because ghc 8.2 (using 3.9) is now in unstable and 
built.
I also uploaded ghc 8.4 that uses llvm 5.0, so maybe we will move forward in a 
few weeks with this one.

For llvm 6.0, I'm sorry but it won't be probably be a real plan for one year or 
so...

I hope this is enough for now, I see 3.8,3.9 are blocked by other 
reverse-dependencies and 5.0 is fairly new now.

Let me know, or close this bug if you think this is ok for now!

Gianfranco

___
Pkg-haskell-maintainers mailing list
Pkg-haskell-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-maintainers