Re: update lang/ghc (preview)

2017-12-16 Thread Karel Gardas 
On Sat, 16 Dec 2017 03:40:28 +0100
Matthias Kilian  wrote:

> Hi,
> 
> On Thu, Dec 14, 2017 at 03:14:36PM +0100, Karel Gardas wrote:
> >  wrote:
> > > Hi to all Haskell fans,
> > >
> > > the diff below updates ghc to 8.2.2.Builds, packages, and correctly
> > 
> > I'm trying todays's CVS and patching with:
> > 
> > cd /usr/ports/lang/ghc
> > patch < /tmp/original_msg.txt
> > 
> > where original_msg.txt is download of email and this fails misserably
> > with a lot of hunk errors and stops on:
> > 
> > |Index: patches/patch-libraries_Cabal_Cabal_Distribution_Simple_Utils_hs
> 
> Then whatever you had in /tmp/original_msg.txt wasn't from my mail.
> 

The problem was in using gmail.com web interface. This thing throws on me patch 
with DOS line-endings and patch does not like that.
This happen also in case of your patch attachment so I investigated a bit since 
I was curious what the h*ll is going on.

Anyway, with using proper MUA, I've been able to get the patch correctly, apply 
it and build ghc-8.2.2 fine.

Fantastic work!

Thanks!
Karel

Re: update lang/ghc (preview)

2017-12-14 Thread Karel Gardas 
On Wed, Dec 13, 2017 at 12:28 AM, Matthias Kilian
 wrote:
> Hi to all Haskell fans,
>
> the diff below updates ghc to 8.2.2.Builds, packages, and correctly

I'm trying todays's CVS and patching with:

cd /usr/ports/lang/ghc
patch < /tmp/original_msg.txt

where original_msg.txt is download of email and this fails misserably
with a lot of hunk errors and stops on:

|Index: patches/patch-libraries_Cabal_Cabal_Distribution_Simple_Utils_hs
|===
|RCS file: 
/cvs/ports/lang/ghc/patches/patch-libraries_Cabal_Cabal_Distribution_Simple_Utils_hs,v
|retrieving revision 1.3
|diff -u -p -r1.3 patch-libraries_Cabal_Cabal_Distribution_Simple_Utils_hs
|--- patches/patch-libraries_Cabal_Cabal_Distribution_Simple_Utils_hs
 19 Sep 2015 07:42:57 -  1.3
|+++ patches/patch-libraries_Cabal_Cabal_Distribution_Simple_Utils_hs
 2 Nov 2016 11:17:56 -
--
File to patch:


do you have any idea how to apply your changes for testing? Thanks! Karel