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: Wed, 23 Apr 2003 22:48:28 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 23 April 2003 12:52:41 -0700, John Cherry wrote:
> As mentioned in other mail, compile statistics for the latest 2.5
> kernels are at:
> However, these statistics are based on defconfig and allmodconfig builds
> (not allyesconfig).  The allmodconfig build contains the riscom8 errors
> that you have observed as well as most other warnings/errors you would
> find in an allyesconfig build.

Do you have any form of automation when dealing with breaking drivers?
If I could reduce the necessary time for creating a working
allyesconfig, that would be quite nice.

Allyesconfig has a couple of advantages. The analysis of object files
is must simpler with just vmlinux to worry about. And some errors
don't show up until link time, not sure if you can catch all of them
with allmodconfig.


If you're willing to restrict the flexibility of your approach,
you can almost always do something better.
-- John Carmack

  reply	other threads:[~2003-04-23 20:36 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 [this message]
2003-04-24  0:01       ` John Cherry
2003-04-24  9:26         ` Jörn Engel
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).