mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Cherry <cherry@osdl.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
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: 23 Apr 2003 17:01:12 -0700	[thread overview]
Message-ID: <1051142471.20793.17.camel@cherrypit.pdx.osdl.net> (raw)
In-Reply-To: <20030423204828.GC26678@wohnheim.fh-wedel.de>

On Wed, 2003-04-23 at 13:48, Jörn Engel wrote:
> 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: http://www.osdl.org/archive/cherry/stability/
> > 
> > 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.

No.  I think Randy Dunlap replied earlier that he spent considerable
time weeding out broken drivers from an allyesconfig configuration. 
This still did not result in a bootable image.

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

> 
> 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.

Agreed.

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.

John


  reply	other threads:[~2003-04-23 23:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:49 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 [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1051142471.20793.17.camel@cherrypit.pdx.osdl.net \
    --to=cherry@osdl.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.com \
    --cc=root@chaos.analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

all inboxes | Powered by JetHome®