linux-kernel - Re: linux-next: origin tree build failure

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100112133252.8b4591bd.sfr@canb.auug.org.au>
Date:	Tue, 12 Jan 2010 13:32:52 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Albin Tonnerre <albin.tonnerre@...e-electrons.com>
Subject: Re: linux-next: origin tree build failure

Hi Linus,

On Mon, 11 Jan 2010 17:26:33 -0800 (PST) Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
> Hmm. I think the real problem is that it allowed LZO to be enabled at all, 
> despite HAVE_KERNEL_LZO not being enabled.
> 
> In other words, I think the config dependencies for RD_LZO are just 
> totally broken.

That may be true, however ...

OK, I grabbed your tree, reverted commit
ac4c2a3bbe5db5fc570b1d0ee1e474db7cb22585 ("zlib: optimize inffast when
copying direct from output") (see my other build error email) and then
the tree built.  :-(  I guess there is something else in the partially
created linux-next today that has triggered this build failure.   I will
investigate further.

Sorry about that.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped