linux-kernel - Re: 2.6.33-next build errors (x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20091229134641.GA10515@rhlx01.hs-esslingen.de>
Date:	Tue, 29 Dec 2009 14:46:41 +0100
From:	Andreas Mohr <andi@...as.de>
To:	Martin Knoblauch <spamtrap@...bisoft.de>
Cc:	linux-kernel@...r.kernel.org, Andreas Mohr <andi@...as.de>
Subject: Re: 2.6.33-next build errors (x86_64 defconfig) on RHEL-4.3

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/