Re: aghermann-0.8.1 to fix #701241

2013-02-26 Thread Yaroslav Halchenko
On Tue, 26 Feb 2013, andrei zavada wrote: > On Mon, 25 Feb 2013 09:44:33 -0500 > Yaroslav Halchenko wrote: > > or as far as I am concerned if you verified with vanilla gcc 4.8 -- it > > should be good enough and just include that closes statement here > Fixed as you said and reuploaded to the

Re: aghermann-0.8.1 to fix #701241

2013-02-25 Thread andrei zavada
On Mon, 25 Feb 2013 09:44:33 -0500 Yaroslav Halchenko wrote: > or as far as I am concerned if you verified with vanilla gcc 4.8 -- it > should be good enough and just include that closes statement here Fixed as you said and reuploaded to the same URL: http://johnhommer.com/academic/code/agherman

Re: aghermann-0.8.1 to fix #701241

2013-02-25 Thread Yaroslav Halchenko
On Sun, 24 Feb 2013, andrei zavada wrote: > Hi Yaroslav & Matthias, > I'm pushing out aghermann-0.8.1 ahead of my usual dev cycle to close bug > #701241, which is FTBSF with g++-4.8. Although this bug has been opened > against an ancient version (0.6), it has indeed persisted until 0.8. > I

aghermann-0.8.1 to fix #701241

2013-02-24 Thread andrei zavada
Hi Yaroslav & Matthias, I'm pushing out aghermann-0.8.1 ahead of my usual dev cycle to close bug #701241, which is FTBSF with g++-4.8. Although this bug has been opened against an ancient version (0.6), it has indeed persisted until 0.8. I was able to compile 0.8.1 with 4.6, 4.7 and the latest s