Date: Tue, 29 Dec 2009 14:46:41 +0100
From: Andreas Mohr <andi@lisas.de>
To: Martin Knoblauch <spamtrap@knobisoft.de>
Cc: linux-kernel@vger.kernel.org, Andreas Mohr <andi@lisas.de>
Subject: Re: 2.6.33-next build errors (x86_64 defconfig) on RHEL-4.3
Message-ID: <20091229134641.GA10515@rhlx01.hs-esslingen.de>
References: <55527.63156.qm@web113308.mail.gq1.yahoo.com> <696574.90670.qm@web113305.mail.gq1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <696574.90670.qm@web113305.mail.gq1.yahoo.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1078
Lines: 26

Hi,

On Tue, Dec 29, 2009 at 01:50:12AM -0800, Martin Knoblauch wrote:
>  Not surprisingly, the problem still exists in next-20091229 :-) But actually, I think it might be even as old as 2.6.31-rc3. See
> 
> http://lkml.org/lkml/2009/7/14/120
> 
> for reference. Different (still older toolchain), but very similar failure.
> 
> @Andreas: did you ever had this resolved? I never saw a followup

Sorry, I don't remember that any more (perhaps removing some CONFIG
fixed it), especially since this problem was then overlayed by
a __udivdi3 problem in the same low-versioned environment:
http://lkml.org/lkml/2009/10/9/230

I thus decommissioned that RHEL3 installation and downgraded to RHEL5
(it managed to do away with any custom kernel builds entirely, among
other things - an interesting approach to fix the problem)

Andreas Mohr
--
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/