archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <>
To: John Cherry <>
Cc:, Timothy Miller <>,
	Linux Kernel Mailing List <>
Subject: Re: Can one build 2.5.68 with allyesconfig?
Date: Thu, 24 Apr 2003 11:26:17 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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 script to produce compilation
> results that would benefit what you are doing.  It lives on the
> stability page.

Will do. Thank you!


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

  reply	other threads:[~2003-04-24  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:49 Can one build 2.5.68 with allyesconfig? Timothy Miller
2003-04-22 20:41 ` Valdis.Kletnieks
2003-04-22 20:51   ` Randy.Dunlap
2003-04-22 21:04   ` Timothy Miller
2003-04-22 20:57     ` Valdis.Kletnieks
2003-04-22 22:25       ` Timothy Miller
2003-04-22 21:06 ` Richard B. Johnson
2003-04-23 19:52   ` John Cherry
2003-04-23 20:48     ` Jörn Engel
2003-04-24  0:01       ` John Cherry
2003-04-24  9:26         ` Jörn Engel [this message]
2003-04-22 21:08 ` Sam Ravnborg
2003-04-22 21:19   ` Randy.Dunlap
2003-04-23 11:58 ` Jörn Engel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).