Re: Can one build 2.5.68 with allyesconfig?

From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: John Cherry <cherry@osdl.org>
Cc: root@chaos.analogic.com, Timothy Miller <miller@techsource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Can one build 2.5.68 with allyesconfig?
Date: Thu, 24 Apr 2003 11:26:17 +0200	[thread overview]
Message-ID: <20030424092617.GC17751@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1051142471.20793.17.camel@cherrypit.pdx.osdl.net>

On Wed, 23 April 2003 17:01:12 -0700, John Cherry wrote:
> 
> No.  I think Randy Dunlap replied earlier that he spent considerable
> time weeding out broken drivers from an allyesconfig configuration. 

Yes, it takes manual inspection of some 30 failures, each costing just
a minute or so. But the compile time between those really hurts, it
generates many context switches for my brain.

> This still did not result in a bootable image.

Which may be a good thing. 28MB would have used all my memory not too
long ago. :)

> If you want to build with allyesconfig and continue on when you run into
> errors, just use the -k (keep going) option with make.

Good idea. Maybe that can cut down the context switches.

> Feel free to hack on the compregress.sh script to produce compilation
> results that would benefit what you are doing.  It lives on the
> stability page.

Will do. Thank you!

Jörn

-- 
And spam is a useful source of entropy for /dev/random too!
-- Jasmine Strong