Date: Mon, 30 Jun 2014 15:26:37 +0200
From: Borislav Petkov <bp@alien8.de>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.15.2 build error on AMD64
Message-ID: <20140630132637.GD4766@pd.tnic>
References: <53AE9058.50902@linicks.net>
 <20140628101240.GA6357@pd.tnic>
 <53AE9863.6050102@linicks.net>
 <53AE9F0B.1080207@linicks.net>
 <20140628122322.GC4373@pd.tnic>
 <53AEBE75.9070301@linicks.net>
 <53B063BC.4040200@linicks.net>
 <20140629194403.GB12943@pd.tnic>
 <53B07F99.40600@linicks.net>
 <20140629212423.GE12943@pd.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20140629212423.GE12943@pd.tnic>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org

On Sun, Jun 29, 2014 at 11:24:23PM +0200, Borislav Petkov wrote:
> Btw, I thought you had that gcc 4.2.x from some distro or so. Because
> if it is in some ancient distro, one could install it in kvm and test
> and play with it.

Ok, I did dig out an ancient debian I had lying around here with gcc
4.1.2. The patch I pointed you at does really fix the issue. So all is
fine and solved now. :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/